Using funtion key to change volume of rhythmbox sometimes causes linux to freeze

[Afkpuz]

Binary package hint: rhythmbox

The title pretty much says it all. Sometimes, if I use the function keys on my keyboard to change the volume of rhythmbox, it locks up the whole system. I've never had the problem using the slider volume controls. I'm running a gateway m680 laptop with fiesty.

[Sebastien Bacher (seb128)]

Thanks for your comments. This does not appear to be a bug report as such. We appreciate the difficulties you are facing, but it would make more sense to raise your question in the support tracker. http://launchpad.net/support. That doesn't look like a rhythmbox bug, whatever the software does the system should not be locked

[AymericT (aymeric-thebaud)]

I have the same problem and I have reasons to think that there may be a problem with Rhythmbox (0.11.2).
With Gutsy, when I use a key to change the volume while Rhythmbox is the active window, it hangs for about 20 seconds and the other applications are affected too. However, these control keys work fine with any other gnome application I use (totem for example). Previously I used Feisty with Rhythmbox 0.10 and it didn't happen (everything worked fine).

[Justin (justinemmanuel)]

I have the same problem when changing volume using the switch on the front of my laptop, it freezes every time. It seems to effect the Gnome panels particularly bad. It freezes with banshee as well, Its the main reason why I stick to Amarok. It appears to be a GTK thing.

[Topher (hunt-topher)]

I can confirm this in Gutsy most recent update (I used the "Report a Problem" menu so details should be attached). Whether using Compiz or in Metacity, if I have Rhythmbox as the active window and I use the FN volume keys or the laptop's frontal volume hotkeys to change the volume,

NOTE: I'm not sure what this bug did in the past, but currently it only makes Rhythmbox (and any other applications I switch to) hang for about 20 seconds. When I test this in Compiz, the Rhythmbox window fades dark to indicate nonresponsiveness. Then after 20 seconds or so it returns to normal. As mentioned above, using sliders to change volume works fine. The FN volume keys also work fine AS LONG AS Rhythmbox is not the active window, or if I am switched to another desktop.

I'm running an Inspiron 1520. My device DB key is <8571d049b59a4f8a891c8a773a3b16e1>. I hope this info helps. It would make sense to me if it were an issue with GTK, but on the other hand I've only ever seen this happen with Rhythmbox.

[eugrus (eugrus)]

Rhythmbox buzzes for a long time with the whole Gnome interface when using
keyboard media-keys for volume +/- with an active Rhythmbox window.

Steps to reproduce:
1. Focus in Rhythmbox window with a playing track.
2. Press +/- volume control media keys on the keyboard.

So, now you can't normally use Gnome interface for some time.

[Topher (hunt-topher)]

Eugrus:

I don't experience that buzzing in Rhythmbox when media volume keys are pressed. Instead, as described, Rhythmbox stops responding (although music continues to play) and other windows may even be affected, like Firefox, if I switch to them to wait for Rhythmbox to pull itself together. The fact that other GTK-dependent windows also subsequently freeze up if I switch to them, *could* indicate that the freezup is a GTK problem...

[Hans van den Bogert (hbogert)]

've got the same error as eugrus (accept the buzzing)

why is this bug still invalid, while it is reproducable?
I think it's pretty severe too, as Topher explained.

[Pedro Villavicencio (pedro)]

If you have the same issue as Topher (rhythmbox freezing) you should open a new bug report with a backtrace on it and please do not re open old bugs because you have a similar problem as i said open a new one rather, thanks.

[Afkpuz (alexander-grayson-taylor)]

Since it is much later and I have upgraded to hardy, I do not have this problem anymore

[Justin (justinemmanuel)]

Afkpuz wrote:
> Since it is much later and I have upgraded to hardy, I do not have this
> problem anymore
>
> ** Changed in: rhythmbox (Ubuntu)
> Status: Invalid => Fix Released
>
>
Me too. Since I have upgraded to Hardy the problem has mysteriously
disappeared.

[eugrus (eugrus)]

But I still experience it after all updates!!! :(((((((((

[Pedro Villavicencio (pedro)]

Does the same happens with totem, vlc, amarok or other media player? i don't think it's rhythmbox fault.

[eugrus (eugrus)]

Pedro Villavicencio, no it doesn't (Totem, Vlc, GMplayer).

Only with Rhythmbox.

[Sebastien Bacher (seb128)]

that's not a rhythmbox bug, whatever an application does the system should not freeze, could you attach your /var/log/messages /var/log/syslog after getting the issue?

[Sebastien Bacher (seb128)]

closing since the bug is fixed in hardy for the submitter, if you have a similar issue in hardy you should open a linux bug

[penalvch (penalvch)]

Afkpuz, this bug was reported a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue? If so, could you please test for this with the latest development release of Ubuntu? ISO images are available from http://cdimage.ubuntu.com/daily-live/current/ .

If it remains an issue, could you please run the following command in the development release from a Terminal (Applications->Accessories->Terminal), as it will automatically gather and attach updated debug information to this report:

apport-collect -p linux <replace-with-bug-number>

Also, could you please test the latest upstream kernel available following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine the issue. Please do not test the daily folder, but the one all the way at the bottom. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested. If this bug is fixed in the mainline kernel, please add the following tags:
kernel-fixed-upstream
kernel-fixed-upstream-VERSION-NUMBER

where VERSION-NUMBER is the version number of the kernel you tested. For example:
kernel-fixed-upstream-v3.11

This can be done by clicking on the yellow circle with a black pencil icon next to the word Tags located at the bottom of the bug description. As well, please remove the tag:
needs-upstream-testing

If the mainline kernel does not fix this bug, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-VERSION-NUMBER

As well, please remove the tag:
needs-upstream-testing

Once testing of the upstream kernel is complete, please mark this bug's Status as Confirmed. Please let us know your results. Thank you for your understanding.

[Launchpad Janitor (janitor)]

[Expired for rhythmbox (Ubuntu) because there has been no activity for 60 days.]