Audacious 4.4.2 on Debian 12



I usually put Linux distro's in 3 categories. Distro's like Arch and Fedora tend to run newer kernels, newer versions of glibc, and newer system library versions. Non-LTS Ubuntu would also be in this group to a lesser extent.

Distro's like Ubuntu LTS and Mint, are little ways back. They tend to run fairly current kernels and libraries, but not quite as new as Arch and Fedora. They run slightly older kernels and systems libraries.

Distro's like Debian and Redhat are notorious for running a couple of years behind the curve. For example the Linux 6.1 kernel was released in Dec 2022. Debian 12 still runs this kernel, and Redhat 10 is the first version of Redhat to use a 6.x kernel.
They still run older system libraries. There are ways to install newer kernels on these distro's, but it isn't always straight forward, and sometimes, even if you do upgrade the kernel, that doesn't usually upgrade the system libraries as well.

"Most" ( definitely not all ) packages from sites like pkgs.org come from vendors. The vendors compile applications ( such as Audacious ) against the default kernel and system libraries for their distro. Usually, the packages have to match the system library versions it was compiled against, or it breaks things. You can download the source code and compile your own newer version ( not a trivial task ) and while this will work, the limiting factors of your kernel and system libraries may prevent some functionality from working. There is always the trade off of "more thoroughly tested" distro's that use kernels and system libraries that have been around for a while, vs newer ( sometimes perceived as "less-stable" ) kernels and systems libraries that are fairly new.

you can determine which system libraries Audacious compiles against by checking its build configuration files, such as CMakeLists.txt or configure.ac, depending on the build system it uses. These files typically list the dependencies and libraries required for compilation. https://github.com/audacious-media-player/audacious/blob/master/acinclude.m4
It looks like it requires GTK 3.18 or newer also.

I have been running the 4.4.4 release for a little while now.
It does look like 4.4.2 exists for Debian Sid.
 
Last edited:
IDK about pkgs.org since I don't use the site, but I will warn this: Audacious 4.4-2 is not compatible with Debian 12, even if you install deps from backports -- not all are up to date.
Also, I'll warn that installing outside your repos is a bad idea and I don't just mean security-wise, you can break stuff. This is one of many reasons why AppImages and Flatpaks/Snaps exist (though I only use AppImages).

If you must, must, must have the latest...

Grab it from Linux Portable Apps as an AppImage. Here's the build script:
(You don't have to install AM/Appman unless you want Appimages managed -- then see the main git).
Just download/copy+paste the script, run it as a normal user, and it'll build the latest upstream into an Appimage. It may take a while depending on your internet. I haven't tried this particular build, but so far everything else I grab from there just plain works -- at the cost of disk space -- so it's my go-to now.

PS: You can't guarantee an AppImage 100%. They're not perfect, but they are pretty good.
 
IDK about pkgs.org since I don't use the site, but I will warn this: Audacious 4.4-2 is not compatible with Debian 12, even if you install deps from backports -- not all are up to date.
Also, I'll warn that installing outside your repos is a bad idea and I don't just mean security-wise, you can break stuff. This is one of many reasons why AppImages and Flatpaks/Snaps exist (though I only use AppImages).

If you must, must, must have the latest...

Grab it from Linux Portable Apps as an AppImage. Here's the build script:
(You don't have to install AM/Appman unless you want Appimages managed -- then see the main git).
Just download/copy+paste the script, run it as a normal user, and it'll build the latest upstream into an Appimage. It may take a while depending on your internet. I haven't tried this particular build, but so far everything else I grab from there just plain works -- at the cost of disk space -- so it's my go-to now.

PS: You can't guarantee an AppImage 100%. They're not perfect, but they are pretty good.
Really too complicate for me, I have tried to install Audacious from the source, but
without success.
I'm not expert on install programs from the source,
and if I don't have a valid and understandable tutorial I'll never succeed.
 
How to install audacious 4.4.2?
All suggestions are welcome!
Merry Christmas!!
 

Attachments

  • Screenshot_2024-12-23_13-50-40.png
    Screenshot_2024-12-23_13-50-40.png
    397.5 KB · Views: 43
preferably
from the source,

This isn't quick and simple... the first thing you need to do is install the compiler suite.


This covers most of it, you don't really need git or cvs, so you can skip that part for now.
You don't really need an IDE either, so you can skip the part about Visual Studio and Eclipse.

After all that's done, download the zip file from - https://github.com/audacious-media-player/audacious/tree/master

There is a drop-down menu near the top that has a "Download zip file" option.

Download and unzip the file, it doesn't really matter where, but usually you would do this in your home directory.
Open a command line console and cd into the audacious directory that you unzipped.


Then you run some "make" commands.

Usually you run "make clean" first, to get rid of any weird junk.

Then you need to run the "./configure" command.


There are some options associated with this, like where you want the compiled program to live.

Then, once you get all the configure options like you want them, just run "make"
This is where the actual compile happens.
Now you may get lucky, and this may compile on the first try. Or you may get some errors, and it may tell you
that you need to install some more development packages. This part is a little trial and error.

If the compile was successful, you would then do a "make install".

Depending on where you told the configure program that you wanted the binary to be installed,
you would then go to.. say.. /usr/local/bin/ for example, and then just type "./audacious"

Assuming all that works, you can add an icon to your launcher menu.
 
Last edited:
This isn't quick and simple... the first thing you need to do is install the compiler suite.


This covers most of it, you don't really need git or cvs, so you can skip that part for now.
You don't really need an IDE either, so you can skip the part about Visual Studio and Eclipse.

After all that's done, download the zip file from - https://github.com/audacious-media-player/audacious/tree/master

There is a drop-down menu near the top that has a "Download zip file" option.

Download and unzip the file, it doesn't really matter where, but usually you would do this in your home directory.
Open a command line console and cd into the audacious directory that you unzipped.


Then you run some "make" commands.

Usually you run "make clean" first, to get rid of any weird junk.

Then you need to run the "./configure" command.


There are some options associated with this, like where you want the compiled program to live.

Then, once you get all the configure options like you want them, just run "make"
This is where the actual compile happens.
Now you may get lucky, and this may compile on the first try. Or you may get some errors, and it may tell you
that you need to install some more development packages. This part is a little trial and error.

If the compile was successful, you would then do a "make install".

Depending on where you told the configure program that you wanted the binary to be installed,
you would then go to.. say.. /usr/local/bin/ for example, and then just type "./audacious"

Assuming all that works, you can add an icon to your launcher menu.
Thank you very much and Merry Christmas!
 
This isn't quick and simple... the first thing you need to do is install the compiler suite.


This covers most of it, you don't really need git or cvs, so you can skip that part for now.
You don't really need an IDE either, so you can skip the part about Visual Studio and Eclipse.

After all that's done, download the zip file from - https://github.com/audacious-media-player/audacious/tree/master

There is a drop-down menu near the top that has a "Download zip file" option.

Download and unzip the file, it doesn't really matter where, but usually you would do this in your home directory.
Open a command line console and cd into the audacious directory that you unzipped.


Then you run some "make" commands.

Usually you run "make clean" first, to get rid of any weird junk.

Then you need to run the "./configure" command.


There are some options associated with this, like where you want the compiled program to live.

Then, once you get all the configure options like you want them, just run "make"
This is where the actual compile happens.
Now you may get lucky, and this may compile on the first try. Or you may get some errors, and it may tell you
that you need to install some more development packages. This part is a little trial and error.

If the compile was successful, you would then do a "make install".

Depending on where you told the configure program that you wanted the binary to be installed,
you would then go to.. say.. /usr/local/bin/ for example, and then just type "./audacious"

Assuming all that works, you can add an icon to your launcher menu.
I have downloaded the files from
Audacious official site https://distfiles.audacious-media-player.org/audacious-4.4.2.tar.bz2

I checked if build essential is installed with:
sudo apt install build essential
build-essential is already the newest version (12.12).
build-essential set to manually installed.
Summary:
Upgrading: 0, Installing: 0, Removing: 0, Not Upgrading: 0

I have checked the gcc version:
gcc --version
gcc (Debian 14.2.0-8) 14.2.0

After I have extract the file in the cd Downloads directory:
$ cd Downloads

[~/Downloads]
└─$ sudo tar -xvjf audacious-4.4.2.tar.bz2

After that I went to the Audacious directory:

[~/Downloads]
└─$ cd audacious-4.4.2

and :

[~/Downloads/audacious-4.4.2]
└─$ ./configure

in the final lines he says:

configure: error: in '/home/sunrise/Downloads/audacious-4.4.2':
configure: error: The pkg-config script could not be found or is too old. Make sure it
is in your PATH or set the PKG_CONFIG environment variable to the full
path to pkg-config.

Alternatively, you may set the environment variables GLIB_CFLAGS
and GLIB_LIBS to avoid the need to call pkg-config.
See the pkg-config man page for more details.

To get pkg-config, see <http://pkg-config.freedesktop.org/>.
See 'config.log' for more details

What is wrong?
 
Last edited:
This is what I meant about trial and error, and adding more development packages.

Note: after a failed attempt to compile, always run "make clean" again to clear out all the failed stuff.
Then run the ./configure command again.

To be honest, I don't have any Debian installs right now, and I can't remember the names of all the packages,
so maybe someone else can step in and help with that part. But for Fedora, the packages are named...

gtk+-devel.x86_64: Development tools for GTK+ (GIMP ToolKit) applications
gtk3-devel.x86_64: Development files for GTK+
PackageKit-glib-devel.x86_64: GLib Libraries and headers for PackageKit
glib-devel.x86_64: Libraries and header files for glib development

Every Distro names their packages slightly different, but they will be similar to these.
You probably already have glib and gtk+ installed on your computer, but you don't have the
development packages for them installed. ( the header files, and things needed to compile them ).

The thing is, some of these packages sometimes require other packages. So after you install these,
it may tell you that you need to install some other packages. The other thing that can happen, is that sometimes
the development version of packages available for your specific distro, may be too old to compile newer
versions of applications.

AppImages and Snap may seem like a lot of work, but they are much easier than compiling your own.
 
Last edited:
This is what I meant about trial and error, and adding more development packages.

Note: after a failed attempt to compile, always run "make clean" again to clear out all the failed stuff.
Then run the ./configure command again.

To be honest, I don't have any Debian installs right now, and I can't remember the names of all the packages,
so maybe someone else can step in and help with that part. But for Fedora, the packages are named...

gtk+-devel.x86_64: Development tools for GTK+ (GIMP ToolKit) applications
gtk3-devel.x86_64: Development files for GTK+
PackageKit-glib-devel.x86_64: GLib Libraries and headers for PackageKit
glib-devel.x86_64: Libraries and header files for glib development

Every Distro names their packages slightly different, but they will be similar to these.
You probably already have glib and gtk+ installed on your computer, but you don't have the
development packages for them installed. ( the header files, and things needed to compile them ).

The thing is, some of these packages sometimes require other packages. So after you install these,
it may tell you that you need to install some other packages. The other thing that can happen, is that sometimes
the development version of packages available for your specific distro, may be too old to compile newer
versions of applications.

AppImages and Snap may seem like a lot of work, but they are much easier than compiling your own.

Thank you very much, in fact in reference to your answer, I installed glib2.0 and gtk+3.0 and I was asked to install another package whose name I don't remember. and I stopped the installation because I thought that later I would have to install another one and so on...
I'll try again...
 
Last edited:

Members online


Top