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 678234 - Songs often sit for a long time at 0:00 or play at the wrong speed
Songs often sit for a long time at 0:00 or play at the wrong speed
Status: RESOLVED DUPLICATE of bug 676689
Product: rhythmbox
Classification: Other
Component: playback
2.96
Other Linux
: Normal normal
: ---
Assigned To: RhythmBox Maintainers
RhythmBox Maintainers
Depends on:
Blocks:
 
 
Reported: 2012-06-17 03:06 UTC by Chris
Modified: 2012-06-17 03:09 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Chris 2012-06-17 03:06:53 UTC
If I double-click a song in rhythmbox, or hit the next song button, the song always plays fine. However, if I let a song end naturally, and Rhythmbox moves onto the next song, often it will sit at 0:00 not playing the song. The pause button is present, so it seems part of rhythmbox thinks it's playing. Pausing and unpausing the song does nothing. Pushing next song or double-clicking a song works fine. If I click a spot on the song position slider, then the song will play from that point immediately as it should.

Sometimes if I wait long enough while it's sitting at 0:00 (over 10 minutes usually), rhythmbox will do something absurd like skip several minutes of the song and play from there, or play the song at fast speed entirely within several seconds and do the same thing with several more songs before fixing itself.

I've already tried deleting all of Rhythmbox's config stuff from my user account, but even from a fresh setup it seems to do this still.
Comment 1 Jonathan Matthew 2012-06-17 03:09:29 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 676689 ***