xmms, when compiled with gcc 3.1, crashes whenever one tries to select a different track while a track is already playing. This means double clicking on the playlist or simply hitting the >| (fast forward to next track) button. xmms also crashes after playing just one track (i.e. the moment it tries to advance to another track on its own, with no user input) xmms was compiled with "USE=-gnome" and CHOST="i686-pc-linux-gnu" CFLAGS="-march=i686 -O3 -pipe -fomit-frame-pointer" CXXFLAGS="-march=i686 -O3 -pipe -fomit-frame-pointer"
This behavior manifests itself when using the 'arts' output module, but does not when using the 'alsa' output module (in other words, xmms works fine with the alsa output module). When it crashes (running via the arts output module), the following appears at the command line: [code] <Init> : Avifile CVS-020612-21:14-3.1 <Init> : Available CPU flags: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 mmx fxsr sse <Init> : 1004.53 MHz Pentium III (Coppermine) processor detected <LDT_Keeper> : Installed fs segment: 0x40017000 mcop warning: user defined signal handler found for SIG_PIPE, overriding Segmentation fault You've probably found a bug in XMMS, please visit http://bugs.xmms.org and fill out a bug report. Segmentation fault You've probably found a bug in XMMS, please visit http://bugs.xmms.org and fill out a bug report. [/code]
I forgot to also mention that compiling xmms with gnome libraries (sanse the USE="-gnome" variable) did not have any effect on the behavior. Arts still crashes xmms, alsa does not.
You're probably using xmms-arts, right? it's this plugin that doesn't work, selecting for example the OSS audio output, and runnin "artsdsp xmms" instead of just "xmms" then fixes this..
This is an upstream bug then?
