OP
Audacious 4.4.2 on Debian 12
- Thread starter hacktheworld
- Start date
OP
hacktheworld
Active Member
I type on the terminal:
audacious %U
the output is:
audacious: error while loading shared libraries: libaudcore.so.5: cannot open shared object file: No such file or directory
Attachments
OP
hacktheworld
Active Member
The version of audacious on the terminal: on the terminal:
$ audacious -v
Audacious 4.4.2 (unknown build)
$ audacious -v
Audacious 4.4.2 (unknown build)
CaffeineAddict
Well-Known Member
Seems like build script didn't do things properly or perhaps you built debug version of audacious.
Dynamic linker is responsible for embedding references to shared libraries and according to this output it was supposed to be installed but was not, maybe all you need is locating the so and creating soft link to it in place where dynamic linker is expecting it.
Yep, what @CaffeineAddict said. That is literally the core audio component. Try installing the current (your Deb 12):
It should work as you built Audacious against your existing system.
If you have issues, remove it and grab the source package here: https://packages.debian.org/sid/libaudcore5 and try to build it against your system (note I sent you to unstable because that's where the 4.4-2 audacious is).
apt-get install libaudcore5It should work as you built Audacious against your existing system.
If you have issues, remove it and grab the source package here: https://packages.debian.org/sid/libaudcore5 and try to build it against your system (note I sent you to unstable because that's where the 4.4-2 audacious is).
OP
hacktheworld
Active Member
Thank you, but nothing to do
Audacious 4.4.2 do not work.
I'll try to reinstall it from scratch another day.
Last edited:
According to the site:
I guess it affects OP... I know in one of the XFCE4 releases, the wallpaper setter from Thunar didn't work right. Even though it was easy to fix -- adding a custom action -- just knowing the bug was there, well, 'scuse the pun, "bugged" me, lol.
OP
hacktheworld
Active Member
sudo apt-get install libaudcore5
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Note, selecting 'libaudcore5t64' instead of 'libaudcore5'
libaudcore5t64 is already the newest version (4.4-2).
libaudcore5t64 set to manually installed.
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
OP
hacktheworld
Active Member
sudo apt-get install libaudcore5
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Note, selecting 'libaudcore5t64' instead of 'libaudcore5'
libaudcore5t64 is already the newest version (4.4-2).
libaudcore5t64 set to manually installed.
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
OP
hacktheworld
Active Member
I' trying to install audacious plugin:
~/Downloads/audacious-plugins-4.4.2]
└─$ ./configure
output:
Package 'json-glib-1.0', required by 'virtual:world', not found
Consider adjusting the PKG_CONFIG_PATH environment variable if you
installed software in a non-standard prefix.
Alternatively, you may set the environment variables JSON_GLIB_CFLAGS
and JSON_GLIB_LIBS to avoid the need to call pkg-config.
See the pkg-config man page for more details.
I have installed 'json-glib-1.0' with:
sudo apt-get -y install libjson-glib-1.0-0
output:
libjson-glib-1.0-0 is already the newest version (1.10.6+ds-1).
but the same message always comes out:
Package 'json-glib-1.0', required by 'virtual:world', not found
Consider adjusting the PKG_CONFIG_PATH environment variable if you
installed software in a non-standard prefix.
Alternatively, you may set the environment variables JSON_GLIB_CFLAGS
and JSON_GLIB_LIBS to avoid the need to call pkg-config.
See the pkg-config man page for more details.
But if I type:
sudo apt install audacious audacious-plugins
the output is: audacious is already the newest version (4.4-2).
audacious-plugins is already the newest version (4.4-1).
Summary:
Upgrading: 0, Installing: 0, Removing: 0, Not Upgrading: 0
I will try to install audacious 4.4.1
~/Downloads/audacious-plugins-4.4.2]
└─$ ./configure
output:
Package 'json-glib-1.0', required by 'virtual:world', not found
Consider adjusting the PKG_CONFIG_PATH environment variable if you
installed software in a non-standard prefix.
Alternatively, you may set the environment variables JSON_GLIB_CFLAGS
and JSON_GLIB_LIBS to avoid the need to call pkg-config.
See the pkg-config man page for more details.
I have installed 'json-glib-1.0' with:
sudo apt-get -y install libjson-glib-1.0-0
output:
libjson-glib-1.0-0 is already the newest version (1.10.6+ds-1).
but the same message always comes out:
Package 'json-glib-1.0', required by 'virtual:world', not found
Consider adjusting the PKG_CONFIG_PATH environment variable if you
installed software in a non-standard prefix.
Alternatively, you may set the environment variables JSON_GLIB_CFLAGS
and JSON_GLIB_LIBS to avoid the need to call pkg-config.
See the pkg-config man page for more details.
But if I type:
sudo apt install audacious audacious-plugins
the output is: audacious is already the newest version (4.4-2).
audacious-plugins is already the newest version (4.4-1).
Summary:
Upgrading: 0, Installing: 0, Removing: 0, Not Upgrading: 0
I will try to install audacious 4.4.1
Last edited:
OP
hacktheworld
Active Member
I have installed audacious 4.4.1
I type on the terminal:
audacious
the output is:
ERROR plugin-init.cc:155 [start_required]: No output plugin found.
(Did you forget to install audacious-plugins?)
zsh: IOT instruction audacious
If I type on the terminal:
sudo apt install audacious audacious-plugins
the output is:
audacious is already the newest version (4.4-2).
audacious-plugins is already the newest version (4.4-1).
Summary:
Upgrading: 0, Installing: 0, Removing: 0, Not Upgrading: 0
At this point I am confused.
I type on the terminal:
audacious
the output is:
ERROR plugin-init.cc:155 [start_required]: No output plugin found.
(Did you forget to install audacious-plugins?)
zsh: IOT instruction audacious
If I type on the terminal:
sudo apt install audacious audacious-plugins
the output is:
audacious is already the newest version (4.4-2).
audacious-plugins is already the newest version (4.4-1).
Summary:
Upgrading: 0, Installing: 0, Removing: 0, Not Upgrading: 0
At this point I am confused.
Last edited:
You have 3 choices here:
Option A:
Find libaudcore5t64.so -- should be in /usr/lib/ or /lib/. Let's suppose it's in /usr/lib/.
Just copy it: cp /usr/lib/libaudcore5t64.so /usr/lib/libaudcore5.so
(Note: check they do have .so extensions, canonically they should, but there are exceptions -- Mozilla cough cough).
This is considered a little hacky, but may work as it may just be a package naming thing where libaudcore5 is a metapackage for all versions and libaudcore5t64 is the actual package/library.
Option B:
To speed things up, I went ahead and built you the AppImage (credits to Ivan-HC for his amazing buildscript repo and Appman):
Download it: https://mega.nz/file/XnomELZA#MYUVG7IWoS7P8jgf0y5cpZyf7c1QxjRVW_NlAkdSRyY
before December 30th GMT+2 (UTC+2).
Then:
chmod +x audacious.AppImage./audacious.AppImage -- run itYou can put it wherver you want, but to ben canonical, I'd suggest:
mkdir -p $HOME/.local/lib/audacious $HOME/.local/bin/cp audacious.AppImage $HOME/.local/lib/audacious/ln -s $HOME/.local/lib/audacious/audacious.AppImage $HOME/.local/bin/audacious
PS: If you're wary of a third-party, it is totally understandable, run ./audacious.AppImage --appimage-extract and check the files.
Option C:
Go to Ivan's github and install Appman: https://github.com/ivan-hc/AppMan
When the installer runs it will ask you "AM" or "Appman", choose "Appman" as this isolates things to your current user.
Then it is as simple as:
appman -ia audaciousYou can use appman for a growing number of software. Or, if you're like me and don't want stuff that manages packages, you can always make a chroot of a VM to run Appman in to build Appimages and then copy them as above.
PS: If you don't trust third-party stuff, copy + paste each script into ChatGPT and ask "What does this do?" "What security issues are here" and so forth. Or, as mentioned, use a chroot/VM (or Docker if you want to complicate things).
Your choice. Let me know ASAP if you don't go for my build so's I can kill the public link. I don't like leaving any access to any of my cloud drives, even the dev ones.
OP
hacktheworld
Active Member
Thank you very much really, I choose the option B that is the Appimage, I downloaded it, I gave it permission to run as a program: and I didn't have to do anything else. I just have one question to ask you: why doesn't the Appimage program have the audio output plugin for pipewire?
Last edited:
Flatpak has version 4.4. Much easier to install than trying to install from source.
Follow the setup guide: https://flathub.org/setup/Debian
Then you can install Audacious:
Follow the setup guide: https://flathub.org/setup/Debian
Then you can install Audacious:
Code:
flatpak install flathub org.atheme.audaciousNot 100% sure but it may be because Pipewire is still optional in Debian 12. There are some libs installed with 12, but PipeWire itself is not the default sound server (unless you're running Gnome3 -- according the the release info). So unless you've explicitly installed PipeWire as a replacement, then it could be the cause. Also could the a dependency thing. I'll know when I get a chance to fire up my Testing (now Trixie) image. Will let you know.
@dos2unix :-
Install Audacious on Linux | Snap Store
Get the latest version of Audacious for Linux - Lightweight audio playersnapcraft.io
Heh.
Whilst I agree that Snaps and Flatpaks are certainly making life easier for many of us, you know the one thing I don't like about them?
The fact that the "stores" want to install 'em directly to your machine, there & then. I'm not at all sure as that's a good idea.
Concurring with @Fanboi , I too have always been a long-standing proponent of AppImages (so far as Linux portable-apps go). I prefer 'em, for the simple reason that you download 'em first, THEN get them up-and-running. I like the sense of having SOME control over the process, y'know? (And when you're finished - and you simply delete them.....they're gone. There isn't still some "framework" hanging around).
I can understand WHY the "stores" are set-up like that. It makes life simple for noobs.....and it cuts-out the somewhat convoluted process of installing 'em yourself via the terminal.
Ah, well. "Each to their own..."
@ron.alan :-
I'm with Ron on this one. I tend to prefer older versions of everything; OSs, software.....so long as it's LTS. And STABLE.
I'm a lazy bugger. I admit it. If summat does what I want, it works A-OK and I'm happy with it, I just do NOT see the point in endlessly tiffling & messing about, constantly & never-endingly updating everything just because it's there.
I take the view, "If it works.....why try to 'fix' it..?" I also take the view that half the time, developers release as much in the way of upgrades/updates/fixes/patches to things as they do largely to justify their own existence. 95% of the time, it's not system-critical stuff. It's simply stuff that's "nice to have".....but in no way is it actually necessary.
I know, I know. I'm a philistine. A dinosaur, at that.....but to me, an OS & software are there to be used. The OS on its own is NOT the "be-all & the end-all". (Frankly, without software, ANY OS is about as much use as a chocolate teapot. Which is to say, it's pretty pointless by itself).
I'm now heading back under my rock.....
Toodle-pip!
Mike.
Last edited:
OP
hacktheworld
Active Member
Thank you very much!
Actually, I agree with you. I avoid them, when possible, but it isn't always possible, especially if you're a newbie
that doesn't have a lot of experience compiling source code.
I'm of the opinion, there is stable, and then there is stable. I don't use Arch because most things are a little "too new"
and untested for me. Bit on the other hand, I don't use things that are 2 or 3 years old either.
I've found that usually if it's stable for a few weeks, or a couple of months, then it's usually stable enough to last... ummm... forever?
Forever is a long time, but I think you know what I mean. Part of my job requires testing new chip-sets.
That includes sound chips, network-chips, wi-fi chips, i-scsi cards, video cards, and USB peripherals. We literally have thousands of computers here. I don't "own" any of them, but I own the operation of them. If the video. or storage, or network, or in some cases even the sound doesn't work on them... it's on me.
I would say we buy ... on average... over a dozen computer systems a month. Mostly servers, but some laptops and desktops also. The computer models we bought last year aren't available anymore. We don't buy used or rebuilt computers.
So then, we usually buy "one" of some model, test the heck out of it for a few weeks, (maybe a month) and then if everything works good, we buy 10 more ( or whatever the situation calls for ) I think the largest order was 64 servers at one time.
Imagine ordering all those in to find out they won't work on your network, or connect to your storage, or run your virtual machines.
Even my home computer are relatively new. I have one laptop that is seven years old, but my two main daily's are both less than a year old. Everything else is somewhere in between. I have some systems that the 3.x and 4.x kernel will not run on. Let me re-phrase that, the kernel runs on them, however that kernel doesn't have the drivers I need. In some cases, I can download and compile them, but more often than not, I use a newer kernel that already has the drivers, then everything just works.
Newer isn't always better, but old stuff will break sooner or later, and then you don't always have to option to replace it with "old stuff".
None of our servers are over 7years old. The vendors won't usually support hardware after that, or if they do... the price goes up substantially. It's usually cheaper to buy a new server.
Last edited:
