new Audacious broken

mindfall · 2007-11-08 19:21:26

Audacious is in bad shape after the update.

* Playing a mp3 crashes Audacious instantly. Terminal output is "illegal instruction". Vorbis works.
* Volume slider doesn't work, checking "software volume control" has no effect
* Gui updates are strangely slow; I can watch dialog windows being drawn, moving the player around on the desktop is slow, the visualization freezes for quite a moment after seeking. Not really important, but there does seem to be a problem somewhere.

Do others have these issues as well? It's my favorite piece of software, and right now it's unusable

Cerebral · 2007-11-08 19:23:35

The illegal instruction was the result of an over-optimized build - apparently configure overrode my make flags - I've gotta get that fixed. (FS report here: http://bugs.archlinux.org/task/8568)

I haven't heard any problems with the volume slider or GUI updates though - however it might be related

Last edited by Cerebral (2007-11-08 19:25:36)

mindfall · 2007-11-08 19:36:48

phew thanks for notice; good to hear it's just a bad build
I already looked through bugtracker but somehow have overlooked the report.
Time to start the abs engines..

Cerebral · 2007-11-08 23:21:53

Can you try the audacious-plugins package at http://www.archlinux.org/~travis/pkg/au … pkg.tar.gz with the stock audacious-player (pacman -S audacious-player) and see if that fixes the problem?

mindfall · 2007-11-09 01:45:43

Hooray

Thank you, much better. Mp3s play again and software volume works too. Slowness in visualization while seeking is gone too.
Well, the volume slider behaves a bit weird (linear rather than logarithmic, causing it to be already nearly full quite @ 50%) but I suppose that's an upstream thing.

Cerebral · 2007-11-09 05:03:12

Awesome - I'll push the fixed version to the repos

KimTjik · 2007-11-09 14:54:22

Maybe this will be fixed then, but in my case audacious doesn't work at all besides "running a stress test of the CPU"! As it is now it won't show up at all but keep on running as process furiously.

I didn't have any old audacious package to roll back to so I'll have to wait. I've tried these combinations in vain:

"audacious-player-1.4.0-1-i686.pkg.tar.gz" with "audacious-plugins-1.4.0-1-i686.pkg.tar.gz"

and

"audacious-player-1.4.0-1-i686.pkg.tar.gz" with "audacious-plugins-1.4.0-2-i686.pkg.tar.gz"

Should I make a bug report, or could this be viewed as an identical issue with a slightly different symptom?

Cerebral · 2007-11-09 14:59:16

KimTjik - I'm a bit confused by your phrasing, so let me see if I understand what you're trying to say.

When you run audacious 1.4.0, using either plugins version 1.4.0-1 or 1.4.0-2, no window appears, however the process starts and your CPU climbs to 100%?

This shouldn't be the same issue - feel free to submit a bug report for it. Please include the following:

. versions of audacious-player and audacious-plugins
. steps to reproduce
. output after running audacious at the command prompt - if no output, explicitly say so
. perhaps the last little bit of the output of strace audacious before you kill the process

KimTjik · 2007-11-09 15:31:23

You understood it correctly. I'll submit a bug report then.

In case someone looks for clues:

- no window and no output if started for command line
- when audacious is killed you see the following:

Audacious has received SIGTERM and is shutting down.
(audacious:7947): GLib-CRITICAL **: g_thread_join: assertion `thread' failed
(mowgli_heap.c:195) [mowgli_heap_alloc]: exception mowgli.heap.internal_error_exception thrown

So at least there's a clue in that it's pointing at libmowgli.

KimTjik · 2007-11-09 18:37:39

I made a request for a closure of the bug task. Reason is that when sweeping the system from any configuration files belonging to audacious and by starting from scratch I got it to work. Pro = it works; con = I don't know what caused the failure.

Thanks!

thayer · 2007-11-10 21:11:43

KimTjik wrote:

I made a request for a closure of the bug task. Reason is that when sweeping the system from any configuration files belonging to audacious and by starting from scratch I got it to work. Pro = it works; con = I don't know what caused the failure.
Thanks!

Ditto... was totally borked for me until I removed ~/.config/audacious.

Also, my skins seem to have disappeared from ~/.local/share/audacious and now I have a symbolic link in ~/.themes that points to /usr/share/audacious/Skins/Default

Last edited by thayer (2007-11-10 21:18:01)

thayer · 2007-11-10 21:25:23

I may open another bug report about this... even with all settings restored to default, I'm still finding that 1 out of 3 times I try to launch audacious it either appears for a split second before vanishing, or it doesn't appear at all and my CPU usage and temps go through the roof.

KimTjik · 2007-11-10 22:07:24

I have to confirm that something is strange with this audacious release. Since I erased config files audacious works, but not until I saw this post I noticed something else: I like to use Streamtuner and when selecting a source configured to start audacious, audacious appears for less than a second and then disappears. However if starting Streamtuner from command line and then do the same as above audacious appears, but this time without doing any useful, except from giving both cores a 100 % load (at least you could argue it's an optimized release making maximum use of a dual-core ). This is the output:

[kimolee@kimtjik ~]$ streamtuner
Failed to load plugin (/usr/lib/audacious/Visualization/projectm.so): libprojectM.so.0: kan inte öppna delad objektfil: Filen eller katalogen finns inte
amidi-plug(amidi-plug.c:amidiplug_init:97): init, read configuration
amidi-plug(i_backend.c:i_backend_load:107): loading backend '/usr/lib/audacious/Input/amidi-plug/ap-alsa.so'
amidi-plug(i_backend.c:i_backend_load:145): backend /usr/lib/audacious/Input/amidi-plug/ap-alsa.so (name 'alsa') successfully loaded
(audacious:10974): GLib-CRITICAL **: g_hash_table_foreach: assertion `hash_table != NULL' failed

Naturally I tried to kill audacious, but that's impossible both as a user and as root. A logout doesn't even work, the only viable option is to reboot the whole system (which gives me some nice Windows flashbacks!). Strange because from the command line you'll see the following:

Audacious has received SIGTERM and is shutting down.

Hence thayer I suppose there's no other option than to file a new bug report. Have you already done that so I just could fill in my information as a comment? It looks at least like we're two now experiencing the exact same problem.

thayer · 2007-11-10 23:00:37

http://bugs.archlinux.org/task/8603

Yep, audacious executed via streamtuner is where I'm really noticing the problem... however, since streamtuner hasn't been updated, I can only assume it's the newest audacious to blame.

KimTjik · 2007-11-11 00:35:47

I've added a comment similar to what I wrote above. It will help to show that the problem isn't system specific (I doubt we have identical systems, and in your case it's not XFCE but Open-box running the desktop).

Let's see what happens.

Last edited by KimTjik (2007-11-11 00:36:10)

Maki · 2007-11-18 00:12:30

i get this when i run the new audacious

[maki@archer Desktop]$ audacious
amidi-plug(amidi-plug.c:amidiplug_init:97): init, read configuration
amidi-plug(i_backend.c:i_backend_load:107): loading backend '/usr/lib/audacious/Input/amidi-plug/ap-alsa.so'
amidi-plug(i_backend.c:i_backend_load:145): backend /usr/lib/audacious/Input/amidi-plug/ap-alsa.so (name 'alsa') successfully loaded
I/O warning : failed to load external entity "/home/maki/.config/audacious/playlist.xspf"
Segmentation fault

i deleted my old audacious config because it also didnt work

jacko · 2007-11-23 21:11:44

I can't seem to get audacious to save any of the settings and I can't seem to find out where to put the eq.preset file. Can anyone help me, This is the first time I ever installed audacious on this OS as well.

I am using audacious 1.4.2 from the AUR repos.

k.mandla · 2007-11-29 23:53:09

Hmm. I lost streaming audio access with the update. Local files play normally, but Shoutcast et al. just hang. Could this be at all related, or is it on my end?

Cerebral · 2007-11-30 03:14:02

do you have neon installed?

k.mandla · 2007-11-30 05:25:57

Aha! That did it. Thank you very much.

How is neon related to audacious? I'd never heard of it before. Was that a change between 1.3 and 1.4? I don't recall installing neon with audacious in the past, although I might have overlooked it.

Again, thanks for taking the time to help with that.

Cerebral · 2007-11-30 12:21:58

Neon's always been an optional dep afaik - it's a library for streaming things over the web. The post-install message mentions this.

kotyz · 2008-03-15 20:26:50

I had same problem with 1.5.0 release, recompilation audacious and audacious-plugins from abs solved this. But I must disable the projectm visualisation plugin, otherwise the compilation failed.

Cerebral · 2008-03-16 19:08:10

kotyz wrote:

I had same problem with 1.5.0 release, recompilation audacious and audacious-plugins from abs solved this. But I must disable the projectm visualisation plugin, otherwise the compilation failed.

which versions of the packages did you use? I accidentally uploaded an SSE2-build of 1.5.0 (audacious-1.5.0-1-i686.pkg.tar.gz) and corrected it shortly after (audacious-1.5.0-2-i686.pkg.tar.gz) - make sure you have 1.5.0-2

Arch Linux

#1 2007-11-08 19:21:26

new Audacious broken

#2 2007-11-08 19:23:35

Re: new Audacious broken

#3 2007-11-08 19:36:48

Re: new Audacious broken

#4 2007-11-08 23:21:53

Re: new Audacious broken

#5 2007-11-09 01:45:43

Re: new Audacious broken

#6 2007-11-09 05:03:12

Re: new Audacious broken

#7 2007-11-09 14:54:22

Re: new Audacious broken

#8 2007-11-09 14:59:16

Re: new Audacious broken

#9 2007-11-09 15:31:23

Re: new Audacious broken

#10 2007-11-09 18:37:39

Re: new Audacious broken

#11 2007-11-10 21:11:43

Re: new Audacious broken

#12 2007-11-10 21:25:23

Re: new Audacious broken

#13 2007-11-10 22:07:24

Re: new Audacious broken

#14 2007-11-10 23:00:37

Re: new Audacious broken

#15 2007-11-11 00:35:47

Re: new Audacious broken

#16 2007-11-18 00:12:30

Re: new Audacious broken

#17 2007-11-23 21:11:44

Re: new Audacious broken

#18 2007-11-29 23:53:09

Re: new Audacious broken

#19 2007-11-30 03:14:02

Re: new Audacious broken

#20 2007-11-30 05:25:57

Re: new Audacious broken

#21 2007-11-30 12:21:58

Re: new Audacious broken

#22 2008-03-15 20:26:50

Re: new Audacious broken

#23 2008-03-16 19:08:10

Re: new Audacious broken

Board footer