GNOME Bugzilla – Bug 144907
allow PrintScreen to work while the main menu is open
Last modified: 2020-11-07 12:16:45 UTC
When you have the main menu open the keyboard is grabbed and PrintScreen doesn't
Investigate whether we can catch the printscreen and invoke the screenshot
action. Might be fairly trivial.
Looks like a GTK+ problem to me: it happens with every menu here. I think
there's already a bug open about this, but I can't find it...
Yeah, I'm just saying we might be able to come up with a hack to make it work
with the panel's main menu.
People take a screenshot of the main menu a lot, we launch
gnome-panel-screenshot from other places, so it may be worth doing if its trivial.
*** Bug 150062 has been marked as a duplicate of this bug. ***
See also bug 100903
ideally it should work with any menu of any application, too.
I cannot take a screenshot when I have an applications menu open either - a real pain as I currently want to take shots of open menus...
Anybody have any idea about this ? If it is a GTK+ issue, as mentionned above, should this not be filed against GTK+ ?
*** Bug 373634 has been marked as a duplicate of this bug. ***
Hi, this is still a problem in Hardy Heron.
The fault has been duplicated into this post
and by the sounds of it the problem isn't easily correctible, because of the menus are caturing all of the input keypresses and simply disgarding CTRL+ commands because they don't relate to a menu item.
However, excuse me if i'm wrong (i'm not a GTK+ programmer), but is it not possible to generate a link between the menu keypress shortcuts and the normal keypress shortcuts.
By this i mean, a key is pressed whilst the user has an open menu, the menu checks the menu shortcut list and if the keypress matches an item in the menu shortcut list it selects the menu item or simply executes the command that would have been run by the user clicking on the relative menu item.
However if the keypress isn't in the menu shortcut list, the menu shortcut engine checks the general shortcut list to see if the keypress matches a general shortcut. If it does it executes the command specified by the general shortcut.
An example of the system would be:
I want to produce a print screen showing someone how to access the Synaptic Package Manager within the System > Administration menu and submenu.
I click on the System menu and then move to the administration submenu and highlight the Synaptic Package Manager Shortcut.
I press the Print Screen key on my keyboard. Immediately the menu engine detects the keypress and checks to see if the keypress relates to a valid shortcut in the menu that is currently open. It doesn't.
Because the menu engine was unable to find a matching shortcut for the keypress it resorts to checking the generic shortcuts for a matching keypress and yes, there is one, the print screen function.
The print screen function is executed and the menu engine can return to idle awating another input from the user.
*** Bug 574938 has been marked as a duplicate of this bug. ***
When the menu is open, multimedia buttons and other global shortcuts such as Ctrl-Alt-D don't work either, see duplicate bug 574938.
Comment #10 Confirmed.
Should we have the description updated to be more specific?
One thing that does work:
Open Firefox, Hit Alt-F (To open file menu), then hit Alt-Tab.
As soon as Alt is hit, the menu closes so Alt-Tab, Alt-E, Alt-V, etc. still work.
I assume this is a work-around that Firefox programmed in? Why can't that also be added in for all GTK+ programs? Is it different in some subtle way that I am missing?
Can 308516 be added as another duplicate? No point in having two identical reports with completely opposite resolutions. Very confusing. It's an assigned bug, yet it's NOTABUG?
May be related to bug 440515 (screensaver does not work either while the main menu is open).
bugzilla.gnome.org is being replaced by gitlab.gnome.org. We are closing all
old feature requests in Bugzilla which have not seen updates for many years.
If you still use gnome-panel and if you are still requesting this feature in a currently supported version of GNOME (currently that would be 3.38), then please feel free to report it at https://gitlab.gnome.org/GNOME/gnome-panel/-/issues/
Thank you for reporting this issue and we are sorry it could not be implemented.