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 594929 - m3u playlist pause itself if clicking forward several times
m3u playlist pause itself if clicking forward several times
Status: RESOLVED DUPLICATE of bug 600425
Product: totem
Classification: Core
Component: Movie player
2.27.x
Other Linux
: Normal normal
: ---
Assigned To: General Totem maintainer(s)
General Totem maintainer(s)
Depends on:
Blocks:
 
 
Reported: 2009-09-11 19:14 UTC by Pedro Villavicencio
Modified: 2010-04-07 16:21 UTC
See Also:
GNOME target: ---
GNOME version: 2.27/2.28


Description Pedro Villavicencio 2009-09-11 19:14:22 UTC 
this report has been filed here:

https://bugs.edge.launchpad.net/ubuntu/+source/totem/+bug/427053

"Using v 2.27.92

Forwarding through an m3u playlist has strange results. I've noticed it will sometimes skip to a random point in the next song and pause it, as opposed to playing from the start. The volume is often muted as well.

Steps to reproduce it:

* Open an m3u playlist with totem
* Press Play (the audio is going to start)
* Press forward a few times

What happened:

Totem pause the playlist (song to play)"

Thanks,
Comment 1 Robin Stocker 2009-09-11 22:27:02 UTC 
Does the skipping to a point also happen when you open the same file separately (not in a playlist)? What is the duration of these files?

It may be because of the new "remember last position" feature (see bug #164918).
Comment 2 Greg Schneider 2009-09-12 02:56:04 UTC 
If I'm understanding this correctly - I opened one of the mp3s and stopped it at a point, then closed totem. Opening the m3u that had it in the playlist and skipping forward to it resulted in that song starting at a different point than what I had stopped it at individually.
Comment 3 Bastien Nocera 2010-04-07 16:21:37 UTC 
I think that was caused by the bug fixed by the patch in bug 600425.

Please reopen if you tested with 2.28.3 or newer and the problem isn't fixed.

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