GNOME Bugzilla – Bug 676888
playbin: When totem finishes the last song in the playlist, it locks up hard
Last modified: 2013-02-05 16:32:50 UTC
I put an album in totem's playlist. When it got to the end of the very last song, the UI locked up; I can move it via the window titlebar but nothing is clickable in the UI, it's kind of greyed out, and the only way to get rid of it is to pkill totem in a terminal. You *can't* reproduce the issue by putting one song in the playlist, forwarding to the last few seconds of the song and letting it finish. You have to play the last song in the playlist in full. So to reproduce: * Put two songs in your playlist * Start playing the last song from the beginning * When the last song finishes, it locks up. I'm not exactly sure if its totem or gstreamer; these are MP3 albums I bought off of Amazon so maybe it's one of the gstreamer plugins. I included their versions below in case it's helpful. totem-3.4.1-3.fc17.x86_64 gstreamer-plugins-good-0.10.31-1.fc17.x86_64 gstreamer-plugins-bad-free-extras-0.10.23-2.fc17.x86_64 gstreamer-tools-0.10.36-1.fc17.x86_64 gstreamer-plugins-base-0.10.36-1.fc17.x86_64 gstreamer-python-0.10.19-3.fc17.x86_64 gstreamer-plugins-bad-0.10.22-4.fc17.x86_64 gstreamer-rtsp-0.10.8-2.fc17.x86_64 gstreamer-plugins-bad-free-0.10.23-2.fc17.x86_64 gstreamer-0.10.36-1.fc17.x86_64 gstreamer-plugins-bad-nonfree-0.10.22-3.fc17.x86_64 gstreamer-plugins-ugly-0.10.19-1.fc17.x86_64
Thanks for taking the time to report this bug. Without a stack trace from the hang it's very hard to determine what caused it. Can you get us a stack trace? Please see http://live.gnome.org/GettingTraces for more information on how to do so. Thanks in advance!
Okay, sorry it has taken me so long to get this trace. It was difficult for me to get it; the bug can only be reproduced if you run totem by searching for it in the shell and clicking on its icon: - It can't be reproduced by running 'totem' from the term (so no terminal spew to grab on lock up) - It can't be reproduced after you run 'ulimit -c unlimited' in the term because you can't reproduce it by running totem from the terminal. - It can't be reproduced by running 'gdb totem' - I have no idea why So I had to reproduce it using the steps in Comment 0, then 'gdb -p `pidof totem`', that's how I got this backtrace. Anyway, here it is. I do see a lot of bacon :) but I don't see any missing symbols, so hopefully it is useful. Thank you for taking a look! ---
+ Trace 230280
Thread 1 (Thread 0x7f61a9d5a9c0 (LWP 3663))
This playsink_reconfigure thing looks familiar. I thought it was fixed, but perhaps only in git. Can you still reproduce this with totem 3.38 and GStreamer 1.0?
Hi Tim-Phillip, it doesn't look like GStreamer 1.0 is available for Fedora 17, so it would be difficult for me to reproduce on this system. :( I have an F18 alpha system available at home though, I can look tonight and see what version of gstreamer it has and try to reproduce if it's 1.0.
Should be on F18 alpha. Might be the same as bug #683574 which I occasionally run into.
(In reply to comment #3) > Can you still reproduce this with totem 3.38 and GStreamer 1.0? Another 8 years before 3.38 :) (In reply to comment #4) > Hi Tim-Phillip, it doesn't look like GStreamer 1.0 is available for Fedora 17, > so it would be difficult for me to reproduce on this system. :( I have an F18 > alpha system available at home though, I can look tonight and see what version > of gstreamer it has and try to reproduce if it's 1.0. F18 has GStreamer 1.0 and the matching Totem version.
Máirín, ping
Hi, I still have F17 and this is still a bug on it - it happened just now with my playlist of MP3 files. I had my colleague Ryan test it with F18, and it doesn't seem to happen in F18.
Thanks for asking him to test it. Let's close this bug then if it works with F18/1.0. It's unlikely to ever get fixed in 0.10/F17, sorry.