Hi! I also experienced the same problem as soon as I upgraded to audacious/1.5.1-1 on a lenny amd64 box.
$ 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 Segmentation fault $ 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 Segmentation fault However, I found out that, after upgrading audacious-plugins audacious-plugins-extra to their (current) unstable versions (i.e.: 1.5.1-1), audacious is again able to start without segfaulting: $ dpkg -l | grep audacious | cut -b 1-60 ii audacious 1.5.1-1 ii audacious-plugins 1.5.1-1 ii audacious-plugins-extra 1.5.1-1 ii libaudclient1 1.5.1-1 ii libaudid3tag1 1.5.1-1 Hence, it seems that the problem lies in the dependencies being not strict enough... Package audacious/1.5.1-1 depends on audacious-plugins (>= 1.5.0) and recommends audacious-plugins-extra (>= 1.5.0), audacious-plugins-extra (<< 2.0~). I think it should instead depend on audacious-plugins (>= 1.5.1), recommend audacious-plugins-extra (>= 1.5.1), audacious-plugins-extra (<< 2.0~), and maybe conflict with audacious-plugins-extra (<< 1.5.1). Is this correct, or am I completely off-track? -- http://frx.netsons.org/doc/index.html#nanodocs The nano-document series is here! ..................................................... Francesco Poli . GnuPG key fpr == C979 F34B 27CE 5CD8 DC12 31B5 78F4 279B DD6D FCF4
pgpJjClpWziFk.pgp
Description: PGP signature
