Giving a short re-summary of the problem: when using rhythmbox, if a
user changes the system volume by using function keys or "special"
volume keys (such as the ones HP puts on their laptops these days), the
system will temporarily hang. Sound continues to play with no problem.

When I intentionally force this bug to happen with a system resource
monitor open, the resource monitor will continue to stream and show that
nothing unusual is happening; that is, there are no resource hogging
events going on, at least from the system monitor's report. However,
this problem seems to block all non-system processes. For example, if I
invoke this bug, rhythmbox will freeze, but I will still be able to
switch desktops and use system menus. However, other running processes
(such as firefox or gedit) will be frozen as well. All non-system
processes unfreeze at the same time, somewhere around 5-15 seconds after
the problem starts.

As noted before in previous bug comments
(https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/144330), this
problem occurs exclusively when two things are true:

1)Rhythmbox has focus (i.e. isn't minimized),
2)Rhythmbox's "Browse" window is open (accessible via View->Browse) and has 
never been closed. 

I've noted that if you open Rhythmbox, then close the "Browse" window
and re-open it, this problem goes away. However, this problem seems to
randomly return every few weeks, and I cannot figure out a pattern
causing it to return.

To recreate this bug yourself, do the following:

1)Open rhythmbox,
2)Ensure that the "Browse" window is open (menu: View->Browse),
3)Begin playing a song,
4)Change the volume using a function key.

Again, the problem seems to be intermittent based on the usage of the
"Browse" window. The problem may also be related to the amount of songs
Rhythmbox is keeping track of. I have ~5000 songs in my library, so
there may be a problem related to the browse window reading a large song
list.

Note that I have NOT tried running rhythmbox from the command line and
invoking this bug to see what errors pop out. Why? Because whenever the
problem crops up I instinctively "fix" it by closing and opening the
"browse" window before I remember to try logging the error. My
apologies.


** Attachment added: "browse_window.png"
   http://launchpadlibrarian.net/18820433/browse_window.png

-- 
Rythmbox freezes when using keyboard volume keys
https://bugs.launchpad.net/bugs/250695
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to