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 419676 - gnome-screenshot should not take a screenie of itself
gnome-screenshot should not take a screenie of itself
Status: RESOLVED OBSOLETE
Product: gnome-utils
Classification: Deprecated
Component: screenshot
2.20.x
Other All
: Normal normal
: ---
Assigned To: Jonathan Blandford
gnome-utils Maintainers
Depends on:
Blocks:
 
 
Reported: 2007-03-18 11:06 UTC by Thilo Six
Modified: 2011-06-13 20:58 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description Thilo Six 2007-03-18 11:06:27 UTC
Please describe the problem:
I took screenies with gnome-screenshot (via menu where it is set to "gnome-screenshot --interactive") and in the resulting screenies there is also gnome-screenshot shown itself.

see this screenies as examples:
http://librarian.launchpad.net/6848943/screenie.jpg
http://librarian.launchpad.net/6850759/Bildschirmfoto.jpg

this does not happen with "ksnapshot"

Steps to reproduce:
1. take a screenie with gnome-screenshot --interactive, started from menu
2. 
3. 


Actual results:
see above screenies

Expected results:
not to see the gnome-screenshot window in taken screenies

Does this happen every time?
not allways. i also had some screenies that looked as expected.
as from my own testing, it seems to happen more often when gnome-screenshot is started from menu, instead started from cli it seems to work (as tested now, took several screenies with both)
even when started from cli with gnome-screenshot --interactive i had no "bad" screenie now

Other information:

This has been reported in ubuntu before as:
https://launchpad.net/ubuntu/+source/gnome-utils/+bug/93234
Comment 1 Kamil Páral 2007-04-30 13:11:22 UTC
this bug is directly connected with this bug:
http://bugzilla.gnome.org/show_bug.cgi?id=434585
Comment 2 Allan Day 2008-07-20 19:44:13 UTC
I get the same thing on my system. I'm setting the status of this bug to new. Though it might be connected to bug 434585, it seems to be a separate issue and thus deserve a bug of its own.

Thanks Thilo!
Comment 3 Cosimo Cecchi 2011-06-13 20:58:28 UTC
Yeah, I believe this is fixed now.