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 567040 - Print screen does not work when a menu is open
Print screen does not work when a menu is open
Status: RESOLVED DUPLICATE of bug 587063
Product: gnome-utils
Classification: Deprecated
Component: screenshot
2.24.x
Other All
: Normal normal
: ---
Assigned To: Jonathan Blandford
gnome-utils Maintainers
Depends on:
Blocks:
 
 
Reported: 2009-01-08 16:31 UTC by Markus Amalthea Magnuson
Modified: 2010-02-25 11:54 UTC
See Also:
GNOME target: ---
GNOME version: 2.23/2.24


Description Markus Amalthea Magnuson 2009-01-08 16:31:00 UTC 
Please describe the problem:
If I open a menu, for example the System menu on the top panel, and then press my "print screen" key on the keyboard, nothing happens. Same with any contextual menus in nautilus and similar. It seems like you cannot make screenshots with menus open, which also means that you can't make screenshots of menus at all.

Steps to reproduce:


Actual results:


Expected results:


Does this happen every time?


Other information:
Comment 1 Jeff Cai 2009-04-01 02:32:58 UTC 
I can also reproduce this bug. This is really annoying. If I want to grap a screenshot with a menu opened, currently I have to use gimp to do that.
Comment 2 Christian Torregrosa 2009-11-27 01:49:40 UTC 
I have the same problem. A workaround to this is:

On the Desktop menu choose Applications->Accessories->Take Screenshot, then in "Grab after a delay of", put 5 seconds for example.

Press Take Screenshot and, go to your desired menu, and wait for the 5 seconds!
Comment 3 Emmanuele Bassi (:ebassi) 2010-02-25 11:54:17 UTC 
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.

*** This bug has been marked as a duplicate of bug 587063 ***