From Bugzilla Helper: User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.6) Gecko/20040217 Description of problem: After launching xmms for the first time, xmms needed to be changed to use alsa sound. I selected the alsa outputs, then tried to play an ogg file. Xmms outputted the following error within gnome terminal. xmms Unable to connect to UNIX socket /tmp/.esd/socket Unable to connect to UNIX socket /tmp/.esd/socket Segmentation fault You've probably found a bug in XMMS, please visit http://bugs.xmms.org and fill out a bug report. Xlib: unexpected async reply (sequence 0x5f4b)! Version-Release number of selected component (if applicable): arts-1.2.0-1.5, xmms-1.2.9-5.p How reproducible: Always Steps to Reproduce: 1. Launch xmms for the first time (no .xmms directory and files in $HOME.) 2. Click on play. Note that after file selection, xmms wants a viable output. 3. select the alsa sound output 4. Try playing an ogg file again. Actual Results: 1. OK (great! This clears up another bug submitted) 2. Normal behavior. Alsa is not set as default output (It should be defaulted to alsa.) 3. No problem applying alsa output. 4. This crashes xmms in a very short time. Expected Results: xmms to launch, output driver already selected for alsa. Player to output sound in xmms. Additional info: To check if xmms was being negatively effected by arts, I removed arts with the --nodep flag and relaunched xmms. I was able to play an ogg file normally. I am using the GNOME desktop. When launching xmms without arts installed, the following output is displayed in the gnome-terminal. libartsc.so.0: cannot open shared object file: No such file or directory xmms will play correctly. I then reinstalled arts, removed the .xmms directory, relaunched xmms. after setting output to alsa, selecting ogg, selecting play, xmms crashed with the above error. When I relaunched xmms, no files to play were selected, arts was still selected as the output. I also got a dialog box that said some other program may be blocking your soundcard. closing down xmms gives me the below error to the gnome-terminal. xmms Message: artsxmms_open(): Unable to initialize aRts: can't connect to aRts soundserver warning: leaving MCOP Dispatcher and still 146 types alive. Message: artsxmms_open(): Unable to initialize aRts: can't connect to aRts soundserver .again, removing arts allows xmms to function. If arts is reinstalled, it will now not cause xmms to error (unless you remove the xmms directory and go again.)
I think there is an option someplace that tells you whether you want to pipe all sounds true arts or not. I can't remember where though.
*** This bug has been marked as a duplicate of 116764 ***
After rebooting my machine (updates were applied for latest arts and xmms). I tried to simulate the problem again. I was unable to get xmms to segfault. My theory is that there was still something loaded in memory, after the programs were installed. The problem is corrected, if you clear whatever is lingering in memory. My prior tests were ran without restarting X or rebooting. The same kernel version was used. however, when tested with the latest kernel-2.6.3-1.100. I get this error. (.xmms directory removed again for test.) Gdk-WARNING **: shmat failed: error 22 (Invalid argument) I will boot back into kernel-2.6.3-1.97 and see if xmms works properly.
With the kernel-2.6.3-1.97 kernel. I do not get the shmat error. I tried using the 2.6.3-1.100 kernel again and xmms will launch. It just displays this error message before it launches. This happens everytime xmms is launched from gnome-terminal.
Alsa and xmms are OK. Bug closed to free developer resources for more issues.