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 661127 - Rhythmbox unresponsive at the end of a song
Rhythmbox unresponsive at the end of a song
Status: RESOLVED OBSOLETE
Product: rhythmbox
Classification: Other
Component: playback
HEAD
Other Linux
: Normal major
: ---
Assigned To: RhythmBox Maintainers
RhythmBox Maintainers
Depends on:
Blocks:
 
 
Reported: 2011-10-06 21:08 UTC by Jeremy Newton
Modified: 2011-11-24 07:15 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Jeremy Newton 2011-10-06 21:08:59 UTC 
Sometimes, not always, but enough to become an annoyance (about 1 out of 4 songs), Rhythmbox become unresponsive at the end of a song. The interface become completely unresponsive, although it still allows me to close without it hanging/freezing (i.e. instantaneous closing).

I'm using the latest git from git://git.gnome.org/rhythmbox and I can confirm, but not necessarily limited to, using Gstreamer 0.10 FFMpeg Plugin. I'm using GNOME 3.2 with gnome-shell.
I also tend to have rhythmbox on another work space while doing something else when it happens. The only settings I've changed from default settings is the watch library for new files setting and shuffle/play in random order.
Comment 1 Jonathan Matthew 2011-10-07 02:51:10 UTC 
I see something like this occasionally, but I haven't managed to look into it much yet.

Can you provide a stack trace from rhythmbox once it's become unresponsive?  See http://live.gnome.org/GettingTraces for information on how to do this.
Comment 2 Jeremy Newton 2011-10-07 04:24:57 UTC 
I'm a little busy right now, but I'll be sure to get a trace as soon as I possibly can.

I would like to note that I've noticed from my clone/build I took a week or so ago versus the clone I made upon creating this bug, the occurrences seemed to have significantly dropped. I have been able to reproduce one time, which was in a period of time that I would have had it happen at least 3 or 4 times with the former build.
Comment 3 Jeremy Newton 2011-10-12 18:18:34 UTC 
I can't seem to reproduce this with the latest git. I think it must have been fixed or I had an issue with my build. Unless someone else can reproduce this, this issue seems to be gone, I think.