audacious 1.5.1ubuntu1 segfaults at starting

[Pedro Fragoso]

Binary package hint: audacious

Description: Ubuntu intrepid (development branch)
Release: 8.10

audacious:
  Installed: 1.5.1-1ubuntu1
  Candidate: 1.5.1-1ubuntu1
  Version table:
 *** 1.5.1-1ubuntu1 0
        500 http://archive.ubuntu.com intrepid/universe Packages
        100 /var/lib/dpkg/status

Output from segfault:

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
Segmentation fault

[Vidar Braut Haarr (vhaarr+launchpad)]

Seems this is a packaging problem, it's segfaulting because the audacious-plugins package is not at version 1.5.1 in Universe.

From my conversation with ccr on #audacious on irc.atheme.org:

<vhaarr> Hey, I just got a segfault with the latest audacious-1.5.1-1ubuntu1, reported here: https://bugs.launchpad.net/ubuntu/+source/audacious/+bug/243539
<vhaarr> seems to be related to parsing my playlist, a ubuntu motu person suggested it was related to the vfs layer, but apparently the report is missing some symbols
<ccr> hum
<ccr> looks more like stack corruption to me
<vhaarr> (that bug is not reported by me, and not the stacktrace either, but it's the same thing I'm getting)
<vhaarr> I made a separate stacktrace myself and was about to post it when I saw that bug
<vhaarr> http://pastey.net/90123
<vhaarr> but without reading through them line by line and comparing, they seem similar
<ccr> if you have any third-party plugins installed, such as crossfade, those need to be recompiled (or removed)
<ccr> I'd say that most likely this is a case of a binary API incompatible plugin(s)
<vhaarr> I have audacious-plugins-1.5.0-1ubuntu3
<vhaarr> 1.5.1 vs 1.5.0
<vhaarr> I guess that's the problem, then?
<ccr> yes
<ccr> I'm not sure how you managed to install it so?
<vhaarr> but removing that package would render audacious useless anyway, since it contains the mp3 support plugin
<vhaarr> well, the audacious package was upgraded today
<vhaarr> yesterday they were both on 1.5.0
<ccr> but not the plugins?
<vhaarr> no
<ccr> ehh
<ccr> well, just wait that the plugins gets updated too
<vhaarr> https://lists.ubuntu.com/archives/intrepid-changes/2008-June/002604.html
<ccr> in my opinion it's a packaging error, if they allowed core > plugins
<vhaarr> indeed
<vhaarr> ccr: would it be OK if I copy+pasted this conversation into the bug report in launchpad?
<ccr> feel free to

[Pedro Fragoso (ember)]

This was fixed as audacious-plugins 1.5.1 is on Intrepid

[Jesse (sbjesse)]

this doesn't seem to be fixed! i'm upgraded to intrepid in november and i'm now affected by this problem. the output of segfault is exactly the same as that of Pedro... what shall i do?

[Pedro Fragoso (ember)]

Hey jesse. This is fixed on Intrepid. What audacious-plugins are you running?