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 772878 - Taking a screenshot or screencast on Wayland with multiple monitors does not capture all of them
Taking a screenshot or screencast on Wayland with multiple monitors does not ...
Status: RESOLVED DUPLICATE of bug 771502
Product: gnome-shell
Classification: Core
Component: general
3.22.x
Other Linux
: Normal normal
: ---
Assigned To: gnome-shell-maint
gnome-shell-maint
Depends on:
Blocks:
 
 
Reported: 2016-10-13 16:30 UTC by Adam Williamson
Modified: 2016-10-14 15:42 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
example screenshot (422.43 KB, image/png)
2016-10-13 16:30 UTC, Adam Williamson
Details

Description Adam Williamson 2016-10-13 16:30:02 UTC
Created attachment 337621 [details]
example screenshot

Running current Fedora 25, with gnome-shell 3.22.1. I have two monitors attached:

[adamw@adam Pictures]$ xrandr
Screen 0: minimum 320 x 200, current 2160 x 1920, maximum 8192 x 8192
XWAYLAND0 connected 1080x1920+1080+0 480mm x 270mm
   1080x1920     59.96*+
XWAYLAND1 connected 1080x1920+0+0 480mm x 270mm
   1080x1920     59.96*+

if I hit the 'print screen' key to take a screenshot, I get a screenshot, but only one screen's contents are actually visible. There's a big transparent area where the contents of the other screen should be. Attaching an example screenshot - in the big transparent area on the right hand side there *should* be a Firefox window with this very bug report open. :)
Comment 1 Adam Williamson 2016-10-13 17:24:39 UTC
This also affects screencasts (shift-ctrl-alt-r), apparently.
Comment 2 Florian Müllner 2016-10-14 15:42:35 UTC
Thanks for taking the time to report this.
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 771502 ***