Totem fails to jump to times in video

[Av8or1ab]

Binary package hint: totem

When I watch a movie, doesn't matter what format. If I try to jump to a time with the bar below the video, it will jump to a time past the end of the video and freeze. The program does not crash but it fails to work and has to be closed. Here is some further information:

Dist: Hardy Alpha 6
Package: Totem
Version: 2.21.95
Expectation: Go to the time displayed while dragging
What did happen: It jumps way past, in this case the play time indicates (199:09:34 / 1:58:32)
Other: I am using Compiz on an ATI X1400 card with the 8.3 fglrx driver

Feel free to contact me with any more questions

ProblemType: Bug
Architecture: i386
Date: Mon Mar 10 21:13:12 2008
DistroRelease: Ubuntu 8.04
ExecutablePath: /usr/bin/totem-gstreamer
NonfreeKernelModules: fglrx
Package: totem-gstreamer 2.21.95-0ubuntu1
PackageArchitecture: i386
ProcEnviron:
 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: totem
Uname: Linux 2.6.24-12-generic i686

[Pedro Villavicencio (pedro)]

Thanks for your bug report. Please try to obtain a backtrace http://wiki.ubuntu.com/DebuggingProgramCrash and attach the file to the bug report. This will greatly help us in tracking down your problem.

[Pedro Villavicencio (pedro)]

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!.

[Patrik Nilsson (nipatriknilsson)]

A video, i.e. mpeg2, is hard to set to a time to continue.

For example: You see a movie for 30 minutes, switch off the computer and want to continue watching the movie later, then it is hard to set the time to continue because mpeg is a compressed format and totem uses bytes to count time in the movie. One byte is not always corresponding to the same time. When totem is started it seeks the movie-file which gives different positions on the slider.

This makes the very hard to set the time.

[Patrik Nilsson (nipatriknilsson)]

Too make the description still clearer: A variable bit rate format can't be positioned accurately with a fixed time algorithm.

[Dimitrios Symeonidis (azimout)]

Patrik, I cannot find a variable bitrate video on my machine right now, could you attach a small one here as a test case, please?
Thank you

[Patrik Nilsson (nipatriknilsson)]

Dimitrios: I have only a big one, which is copyrighted.

Maybe it is possible to find anything free on the Internet? youtube?

[Patrik Nilsson (nipatriknilsson)]

I finally found one. Hopefully no one cares about it! It is 46 seconds long.

[Patrik Nilsson (nipatriknilsson)]

Dimitrios: Thank you for waiting for the movie...:)
I let you change the status to confirmed!

[Benn Snyder (benn.snyder)]

Opened your movie in totem 2.29.91 (in Lucid development). I was unable to jump to different times (the video froze and the indicated time remained the same). When I didn't try to jump to times, the thing indicating the total time of the movie started at 11:58, then started jumping down quickly down to 46 seconds (actual length of the movie). After the video finished playing, I get
"pa_stream_writable_size() failed: Connection terminated"

VLC 1.0.5 plays the file without problems.

[Omer Akram (om26er)]

I have reported this bug for gstreamer-bad since i believe that could be a more related package than totem. https://bugzilla.gnome.org/show_bug.cgi?id=640950

[Daniel van Vugt (vanvugt)]

Thank you for reporting this bug to Ubuntu.
Ubuntu 8.04 (hardy) reached end-of-life on May 12, 2011.

See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases

We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test. If you then find the bug is still present in the newer Ubuntu version, please add a comment here telling us which new version it is in and change the bug status to Confirmed.