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 754719 - [wayland] screenshot of modal dialog is cropped to the size it overlaps its parent window
[wayland] screenshot of modal dialog is cropped to the size it overlaps its p...
Status: RESOLVED FIXED
Product: gnome-shell
Classification: Core
Component: general
unspecified
Other Linux
: Normal major
: ---
Assigned To: gnome-shell-maint
gnome-shell-maint
Depends on:
Blocks: WaylandRelated
 
 
Reported: 2015-09-08 10:39 UTC by Christian Stadelmann
Modified: 2016-04-07 12:17 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Christian Stadelmann 2015-09-08 10:39:06 UTC 
If you take a screenshot of a modal dialog, the screenshot is cropped to the size the dialog overlaps its parent window.
This issue is specific to wayland.

Steps to reproduce:
1. run gnome-control-center, click on "Network", "+"(Add), "VPN", "OpenVPN".
2. Press Alt+Print to make a screenshot of the currently visible window/dialog

Expected result:
A screenshot of the whole modal dialog. Screenshot size should match window size.

What happens:
A screenshot of the modal dialog only where it overlaps the parent window.

Software versions:
gtk3-3.17.8-1.fc23.x86_64
mutter-3.17.91-1.fc23.x86_64
gnome-shell-3.17.91-1.fc23.x86_64
control-center-3.17.90-1.fc23.x86_64
NetworkManager-1.0.6-2.fc23.x86_64
gnome-screenshot-3.16.2-2.fc23.x86_64
Comment 1 Matthias Clasen 2015-11-30 16:04:31 UTC 
screenshots are implemented in gnome-shell
Comment 2 Matthias Clasen 2015-11-30 16:10:06 UTC 
But I am not seeing this behavior with 3.19.2. Can you still reproduce ?
Comment 3 Matthias Clasen 2015-11-30 16:10:29 UTC 
But I am not seeing this behavior with 3.19.2. Can you still reproduce ?
Comment 4 Christian Stadelmann 2015-11-30 16:42:38 UTC 
I am not using 3.19.x, just 3.18.x (Fedora updates-testing). I can still reproduce this issue there.
Comment 5 Christian Stadelmann 2016-04-07 12:17:29 UTC 
This issue is fixed in 3.20. Thank you!