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 551163 - Global hotkeys don't work when menu opened
Global hotkeys don't work when menu opened
Status: RESOLVED WONTFIX
Product: gnome-panel
Classification: Other
Component: menu
2.22.x
Other Linux
: Normal normal
: ---
Assigned To: Panel Maintainers
Panel Maintainers
Depends on:
Blocks:
 
 
Reported: 2008-09-06 22:10 UTC by Remco
Modified: 2009-06-18 15:33 UTC
See Also:
GNOME target: ---
GNOME version: 2.21/2.22



Description Remco 2008-09-06 22:10:15 UTC
When you open the menu, you can't use keys like "PrintScreen" to create a desktop screenshot, or "Play/Pause" to control Rhythmbox.

Steps to reproduce:

1. Click on the applications menu
2. Make sure the menu is opened
3. Press "PrintScreen"
4. Press "Play/Pause"
5. Press "Volume Up"
6. Press "Volume Down"

Expected behaviour:

The actions as indicated by the buttons are executed.

Actual behaviour:

Nothing happens.
Comment 1 sfnrwpurwhbly 2009-03-04 14:52:26 UTC
To reproduce this bug you don't need to press PrintScreen. Step 3 is not required.

You can right click and open any drop down menu (for example in Firefox or on your desktop), it does not have to be the applications menu. Therefore it takes only three simple steps to reproduce this bug (less than the original version).

Steps to reproduce:
1. Click on the applications menu
2. Make sure the menu is opened
3. Press "Volume Up" or "Volume Down"

The volume isn't changed at all. Muting doesn't work as well.

The bug also occurs in Gnome 2.24.x, running on Ubuntu 8.10 with all updates.
Comment 2 Vincent Untz 2009-06-18 15:33:30 UTC
Yes, it's a limitation of GTK+. You'll notice that it actually happens with all menus (even in apps, not just the main menu. This is a well-known bug which would require difficult work in GTK+. So I'll close as WONTFIX even though that's not the right resolution -- GTK+ people are aware of the issue and will fix it when it will be possible.