GNOME Bugzilla – Bug 315898
[GST 0.8] totem-gsteamer freezes when pausing, advancing, or reversing playback
Last modified: 2006-09-08 12:43:22 UTC
This bug has been opened here: http://bugzilla.ubuntu.com/show_bug.cgi?id=14068 "The version of totem gstreamer in breezy freezes when you pause, advance, or reverse playback. It does NOT happen when using the xine backend. This happens regardless of the file format.. any movie or audio file does this. The program doesn't segfault or crash, the movie/audio just freezes. The program appears to respond.. menues and buttons work.. they just don't affect the playback. If I have more than one media file on the playlist, I can procede to the next one or go back to the previous, but as soon as I attempt to advance, pause, or reverse the playback, the media freezes. I will attach the output of 'totem --gst-debug-level=5 --gst-debug-no-color mediafile.avi' (I didn't paste it inline because it is >400,000 lines. ... http://bugzilla.ubuntu.com/attachment.cgi?id=3358 output of 'totem --gst-debug-level=3 --gst-debug-no-color' debug level 4 and 5 created huge files, so I'm sending debug level 3"
Current version are: gstreamer/gst-plugins0.8 0.8.11 and totem 1.2.0
does changing audiosink fix it? If so, which audiosink is this? esdsink? I cannot reproduce, I think...
Good call. This is with the ALSA sink (0.8.11-0ubuntu2), but not OSS or ESD. It's been happening for several versions at least. Alsa packages: alsa-base 1.0.9b-3ubuntu1 alsa-utils 1.0.9a-4ubuntu1 libasound2 1.0.9-2
Does it happen with: alsasink device=hw:0 alsasink device=plughw:0 alsasink device=dmix alsasink device=default ?
It works with: hw:0 dmix but not with: plughw:0 default I'm using a SB Live 5.1 (which supports hardware mixing, AFAIK), and have it set to output 5.1 audio.
Thanks for the bug report. Without a stack trace from the crash it's very hard to determine what caused it. Can you provide us with one? Please see http://live.gnome.org/GettingTraces for more information on how to do so.
alfredoj69: This isn't a crash being reported, so asking for a stack trace of the crash doesn't make sense. Also, you'll note that one of the developers has already started responding. One more thing to note--click on the light bulb icon next to the reporter's name; you'll note that Sebastien has reported over 1000 bugs, closed a couple thousand and added thousands of comments to other bugs. He'd know if he needed to add a stack trace. ;-) Thanks for getting involved.
current CVS HEAD of Totem and GStreamer now handles that smoothly. Fixed.
0.8 doesn't. Mark and reopen
(Mass-closing of GStreamer-0.8 related Totem bugs) Thanks for the bug report. However, the version you are using is no longer maintained. Please upgrade to the most recent version and open a new bug if the problem persists with a current Totem/GStreamer-0.10 version.