GNOME Bugzilla – Bug 577984
Rhythmbox Music Player: Seek bar problems
Last modified: 2009-04-05 07:52:00 UTC
Version: 0.11.6 To start, I am using multiple libraries. If I select one of my libraries, start playing a song, seek to a point with the seek bar, then play another song, the first song doesn't stop and plays in the background even if I pause. If I go to the Radio section (with a song playing even while Rhythmbox is "paused"), pick a station, start playing it, then pause it, the background song stops as it should have before. If I then go to a different library, play a song, then seek a few times, Rhythmbox crashes. Distribution: Ubuntu 8.10 (intrepid) Gnome Release: 2.24.1 2008-10-24 (Ubuntu) BugBuddy Version: 2.24.1
Thanks for taking the time to report this bug. Without a stack trace from the crash it's very hard to determine what caused it. Can you get us a stack trace? Please see http://live.gnome.org/GettingTraces for more information on how to do so. Thanks in advance!
Created attachment 132107 [details] Rhythmbox GDB Stack Trace I had to run gdb manually to get a stack trace since bug-buddy didn't start automatically (probably because the program doesn't "crash", it just hangs indefinitely (as in it's been hanging for 10+ minutes now). This trace was generated using "thread apply all bt" as said in http://live.gnome.org/GettingTraces/Details It was generated while the program was hanging.
This looks like a combination of a few different bugs that were fixed in 0.12.0. Bug 553230, mostly. Any chance you could try 0.12.0? You might be able to find a package for intrepid in some PPA somewhere, but you might have to build it yourself.
I upgraded to a version from getdeb.com (0.12.0) and that seek problem seems to be fixed, but overall this version has more bugs/annoyances (notification area popup does not appear under icon, program closes after last song in library is played, "progress bar" in the bottom right of the program always seems to be moving, higher CPU usage), haha. I'll just stick with the old version for now and/or compile from source sometime.
Since the original problem has been fixed, I'm closing this bug. Most of those issues you mention have already been fixed since 0.12.0, by the way. *** This bug has been marked as a duplicate of 553230 ***