After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 536087 - Totem restarts the movie from the beginning when a subtitle is opened
Totem restarts the movie from the beginning when a subtitle is opened
Status: RESOLVED DUPLICATE of bug 514050
Product: totem
Classification: Core
Component: GStreamer backend
2.22.x
Other All
: Normal minor
: ---
Assigned To: Maintainer alias for GStreamer component of Totem
Maintainer alias for GStreamer component of Totem
Depends on:
Blocks:
 
 
Reported: 2008-06-01 17:09 UTC by Eric Piel
Modified: 2009-11-24 20:14 UTC
See Also:
GNOME target: ---
GNOME version: 2.21/2.22



Description Eric Piel 2008-06-01 17:09:21 UTC
Please describe the problem:
If I add a subtitle to a movie while it is being played, the movie is restarted from the beginning.



Steps to reproduce:
1. Open a movie
2. Go to playlist, right click on the movie, and "select text subtitle..."
3. Open a subtitle


Actual results:
The movie restarts from the beginning.

Expected results:
I expect the movie to keep going on, just with the new subtitle used. If the back-end doesn't support loading subtitles dynamically, but the movie is seekable, it should at least be put back to the closest position.

Does this happen every time?
Yes

Other information:
Comment 1 Bastien Nocera 2008-06-01 18:13:08 UTC
That's how it works, xine-lib can't do any other ways. I expect it to be fixed in Totem when the xine-lib backend is removed...
Comment 2 Eric Piel 2009-07-13 10:07:12 UTC
Reopening, as xine backend has been removed and the bug is still present.
Comment 3 Robin Stocker 2009-11-24 20:14:12 UTC
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.

*** This bug has been marked as a duplicate of bug 514050 ***