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 784085 - surface sizing issues when using zxdg_toplevel_v6::set_fullscreen() with monitors of differing scale
surface sizing issues when using zxdg_toplevel_v6::set_fullscreen() with moni...
Status: RESOLVED OBSOLETE
Product: mutter
Classification: Core
Component: wayland
git master
Other Linux
: Normal major
: ---
Assigned To: mutter-maint
mutter-maint
Depends on:
Blocks:
 
 
Reported: 2017-06-22 10:43 UTC by 28872d13
Modified: 2021-07-05 13:46 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
Patch for weston-fullscreen to allow switching fullscreen output (3.57 KB, patch)
2017-06-22 10:43 UTC, 28872d13
none Details | Review
Screenshot of mutter with two dummy monitors and wrongly displayed surface (164.62 KB, image/png)
2017-06-22 10:45 UTC, 28872d13
  Details

Description 28872d13 2017-06-22 10:43:30 UTC
Created attachment 354239 [details] [review]
Patch for weston-fullscreen to allow switching fullscreen output

When moving surfaces that are already fullscreen between outputs with zxdg_toplevel_v6::set_fullscreen(), the toplevel surface does not get correctly displayed and/or configured when the outputs do not both have the same scale. Depending on the direction of the move and the buffer scale, the surface will be displayed either covering only a portion of the screen or way too large.

Attached is a patch for weston-fullscreen that allows switching between outputs with the "o" key. Just play around with it and you will soon notice it behaving oddly. Everything works fine with weston fwiw. Dragging the window between outputs using the mouse also seems to work with mutter.
I'll also add a screenshot of what the window looks like when moved from output 1 with scale=1 to output 2 with scale=2. The surface is clipped, as can be seen by the blue rectangle.
Comment 1 28872d13 2017-06-22 10:45:24 UTC
Created attachment 354240 [details]
Screenshot of mutter with two dummy monitors and wrongly displayed surface
Comment 2 Jonas Ådahl 2017-06-23 03:47:18 UTC
I suspect that by reverting the commits 27b949d6babb14c87a760ceb4e21b80f0855fa7a, 27ea62a79d9de0cfde3243299a193185d11ede53 and cf1edff9ed0c3f20171e75bbbb5d7c0616f1c38d in mutter it might start working. Those break updating current monitor on movement.
Comment 3 28872d13 2017-06-23 07:06:40 UTC
Reverting these 3 comments does not change anything for me.
Comment 4 GNOME Infrastructure Team 2021-07-05 13:46:31 UTC
GNOME is going to shut down bugzilla.gnome.org in favor of gitlab.gnome.org.
As part of that, we are mass-closing older open tickets in bugzilla.gnome.org
which have not seen updates for a longer time (resources are unfortunately
quite limited so not every ticket can get handled).

If you can still reproduce the situation described in this ticket in a recent
and supported software version, then please follow
  https://wiki.gnome.org/GettingInTouch/BugReportingGuidelines
and create a new ticket at
  https://gitlab.gnome.org/GNOME/mutter/-/issues/

Thank you for your understanding and your help.