Audacious 4.0.5 installed when installing 4.1-2 from test repo [Solved]

[nixon]

No, I might have self compiled it some time ago (but I think this was on mx19 and different laptop) but when I de-install everything seems to be gone.

[dolphin_oracle]

you might look under $HOME/.local/share/applications to see if you have an audacious desktop file that is pointing to some other audacious installation.

[nixon]

No audacious desktop file there.

[seriousness]

I already mentioned this here: https://forum.mxlinux.org/viewtopic.php ... 17#p688417.

The new package 4.2-0.1~mx21+1 really contains audacious 4.2 .

[nixon]

Yep, this worked for me also :) Thanks for the new package,
I wonder what went wrong here, if I am in QT mode it shows 4.2 and if I switch back to GTK I get 4.0.5...
Maybe I forgot to check qt. Nevertheless thanks for all the help :)

[seriousness]

This really is somewhat confusing. I wonder if 4.1 would have shown the correct version, if I had tried to start it in Qt mode.

I will check in Ubuntu Studio, if 4.1 shows the same behavior.

[Stuart_M]

... if I am in QT mode it shows 4.2 and if I switch back to GTK I get 4.0.5...

You are correct in stating the Audacious "About" window will show 4.2.0 while in Qt mode and 4.0.5 while in GTK mode. HOWEVER, if audacious 4.0.5 was not installed before installing audacious 4.2.0, then it will display 4.2.0 in both Qt and GTK modes - it's only when audacious is updated from 4.0.5 to 4.2.0 that the two different versions are show when in fact only 4.2.0 is being used.

By the way, when audacious 4.2.0 is first installed it will be in Qt mode. To go to GTK mode, go to File > Settings > Appearance and click on "Restart in GTK (legacy) mode". Note that once that is done there is no option to go back to Qt mode in the Settings window, at least that I have been able to see. To change modes go to ~/.config/audacious/config and change "use_qt=FALSE" to TRUE. (@seriousness mentioned this problem in another thread.)

Below are two images showing Qt and GTK modes (there is no option to change modes while in GTK mode [lower image]):

Qt:

audacious_Qt_mode.png

GTK:

audacious_GTK_mode.png

----------------------------------------------------------------------------



I tested audacious 4.2.0 in MX-19 and MX-21 with each using a directly-downloaded MX-19/21 ISO (Live Flash Drive). I was never able to install audacious 4.2.0 in MX-19.4. Trying in install it produced the error "Problem detected while installing, please inspect the console output". This is the MX-19.4 console output:

Code: Select all

Hit:1 http://deb.debian.org/debian buster-updates InRelease
Hit:2 http://deb.debian.org/debian buster InRelease
Hit:3 http://mirrors.rit.edu/mxlinux/mx-packages/mx/repo buster InRelease
Hit:4 http://deb.debian.org/debian-security buster/updates InRelease
Get:5 http://mirrors.rit.edu/mxlinux/mx-packages/mx/testrepo buster InRelease [6,791 B]
Get:6 http://mirrors.rit.edu/mxlinux/mx-packages/mx/testrepo buster/test i386 Packages [1,126 kB]
Get:7 http://mirrors.rit.edu/mxlinux/mx-packages/mx/testrepo buster/test amd64 Packages [1,167 kB]
Fetched 2,300 kB in 1s (1,988 kB/s)
Reading package lists...
Reading package lists...
Building dependency tree...
Reading state information...
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 audacious : Depends: audacious-plugins (>= 4.2) but it is not going to be installed
E: Unable to correct problems, you have held broken packages.
Hit:1 http://deb.debian.org/debian buster-updates InRelease
Hit:2 http://deb.debian.org/debian buster InRelease
Hit:3 http://mirrors.rit.edu/mxlinux/mx-packages/mx/repo buster InRelease
Hit:4 http://deb.debian.org/debian-security buster/updates InRelease
Reading package lists...

MX-21.1 installed okay, but it should be noted that if audacious 4.0.5 is installed (Stable Repo) and then audacious 4.2.0 (Test Repo) is installed (Upgrade), it will be fine, but I could never get 4.0.5 working again after that (I re-booted the Live Flash Drive to reset everything). After uninstalling 4.2.0 in the Test Repo I could not open 4.0.5 even though that version was greyed out in the Stable Repo. I tried to re-install 4.0.5 but there was nothing to install (the installer Details window was empty). It is interesting to note that after attempting to re-install 4.0.5 and then cancelling the installation, that it made the audacious 4.0.5 entry become regular text (it was no longer greyed out, and even so, audacious 4.0.5 would not install unless I re-booted to restore all the defaults).

Purging audacious did not help install 4.0.5 after uninstalling 4.2.0. Installing 4.2.0 works fine, either as an upgrade to 4.0.5 or by itself - it's just going back to 4.0.5 from the Test Repo version that the problem occurs. I mention this because users should be aware of this problem if 4.2.0 is going to be tested and they want to go back to the old version.

[seriousness]

Now I got it working. I had to manually upgrade the packages

Code: Select all

libaudtag3

libaudgui5

to the new versions in Test Repo.

[nixon]

I had the same problems when trying to reinstall stable 4.0.5 after checking the 4.1 testing version.
One thing I do is start Audacious with the

Code: Select all

audacious -Q

command in whisker menu to get qt working again.
Could be helpful for further readers.

[Stuart_M]

... One thing I do is start Audacious with the

Code: Select all

audacious -Q

command in whisker menu to get qt working again. ...

For those that don't know, using the -Q option will only work when starting audacious from the Terminal - this option will not change the Qt/GTK setting in the configuration file. When audacious is in GTK mode, launching audacious from the menu, desktop, etc. will only open it in the GTK mode unless it was changed in the configuration file beforehand (audacious must be closed when the configuration file is edited) -OR- audacious 4.2.0 was installed by itself and was not installed as an upgrade from 4.0.5 as explained below.

I just found out that if audacious 4.2.0 (Test Repo) is installed by itself, e.g. it is NOT installed as an upgrade from 4.0.5, then an option will appear in Settings > Appearance to select GTK or Qt. For some reason version 4.0.5 inhibits that option from appearing in 4.2.0 when installed as an upgrade.

The below image is from audacious 4.2.0 when it is installed by itself (not an upgrade from 4.0.5). The below image is from Settings > Appearance and everything inside the below red rectangle does not appear when 4.0.5 is upgraded to 4.2.0. The difference is the option to select Qt mode appears here but does not appear in the same window/version (4.2.0) in Post #27. The image in post #27 is audacious 4.2.0 that was updated from 4.0.5.

audacious_4.2.0_GTK-mode_Qt_option.png