I can load xmms, play my usual playlist and it works fine. Then I choose to stop it and load a new playlist. It shows the new playlist items being changed from the the/path/and/filename to the artist track name. So far so good. Then I will choose play and the button stays depressed and nothing happens. During this time the song name is still being scrolled in the window (visual window?). When I do ANYTHING else, it freezes. I usually have to open a terminal and do killall xmms to close it out. Reproducible: Always Steps to Reproduce: 1. Play a playlist 2. Stop playback 3. Open a new playlist 4. Choose play 5. Curse xmms for locking up again. Actual Results: Locks up Expected Results: Played the playlist or at least given an error if there is one. Since my emerge info, use flags and such are longer than the few lines it says my additional information is, I'll create text file attachments of that info. I figure that would be annoying, but hey, that's what Bugzilla says.
Created attachment 55701 [details] emerge info
Created attachment 55702 [details] package.use
If there is anything I can give please let me know. Thanks.
I can't change the Reproducible option, but it should be "often" instead of Always. Also, here are the results of qpkg -I -v xmms media-sound/xmms-1.2.10-r13 * media-plugins/xmms-oss-1.2.10 * media-plugins/xmms-arts-0.7.1-r1 * media-plugins/xmms-mpg123-1.2.10-r1 * media-plugins/xmms-vorbis-1.2.10-r1 *
I was playing it today using a custom playlist (it started up with it already loaded) and it played for about 30 minutes. It finished up playing the current song then it played KDE's "logging out" sound and just sat there. I tried to close it and it locked up. I opened a terminal, did killall xmms and opened xmms from the terminal Here is the output: -------------------------------------------- libFLAC.so.6: cannot open shared object file: No such file or directory *** glibc detected *** double free or corruption (fasttop): 0x081d41f8 *** Aborted -------------------------------------------- The first line is what it said immediately. Then when it froze when I told it to play I did Ctrl-C and it closed but gave the last two lines.
firstly, do: revdep-rebuild --soname libFLAC.so.6
It no longer complains about libFLAC.so.6 missing, but as far as random crashing I'll have to "post" back on that after a few days. I'll be sure to use it heavily.
Man I was SO hoping that the problem we fixed yesterday was the issue, but alas: it was not meant to be. Today I fired up XMMS via the console/terminal and it automatically loaded my playlist from yesterday. I hit play and it sat there. oookkaaaay. I hit play again. The button "stuck" and it locked up. I hit the "X" in the top right hand corner. Now in order to kill it I'll have to use killall xmms or Ctrl-C from within the terminal that I opened XMMS. Perhaps not. I just switched back over to the terminal window I opened XMMS from and XMMS is closed. I can't swear that I didn't accidentally hit Ctrl-C, but I doubt it. Perhaps it just took forever to close. When I opened XMMS up again the playlist was empty, so I chose my list and it is working. Is this some sort of bizarre user error? Is there a debug option I can turn on to see what XMMS is doing when it "freezes up" like that? Thanks.
what filetype is it playing when it freezes? Does it only crash when playing files of that type? Does it hang when you use a different output plugin? Can you use gdb to figure out where it's hanging? What other plugins do you have installed/enabled? Try removing all the xmms plugins on your system except the input/output plugin you use (just move them somewhere safe). Does it still happen?
After comment #7, it seems okay now. I guess removing the mad plugin went okay, but doing the whole 1. Change USE flag 2. emerge --update --deep --newuse world 3. emerge -p --depclean 4. revdep-rebuild just didn't work for flac. It seems okay now. It will act like it's locking up, but after a few moments it will wakeup and start playing. The file types are .ogg, all .ogg files. The output plugin is OSS. The plugins are listed in comment #4. I've never actually used gdb, but will if you guys need more details. Thanks.
you need to build xmms with CFLAGS="-g" and no -fomit-frame-pointer. Then when it's hanging, in another console run: gdb xmms <process id of xmms> This will bring up a debugging environment in which you can type 'bt' to get a backtrace, 'next' or 'step' to execute the next instruction (step goes into functions while next does not) as well as many more debugging features. For this purpose, you really only need those commands. If youu just hit enter, it repeats the last command. If it's hanging, it's probably looping at one point, so I'd keep stepping until I saw the pattern. Then run bt at the start of the loop.
bumping to herd as i nolonger maintain xmms
Closing for now. Reopen if you still have the same problem.
