Description of problem: I have a two display setup in GNOME Wayland. One DVI, 100% scaled regular display and one Display Link, 150% scaled HiDPI display. When I maximize a window, for example gedit, on the right 150% scaled screen and lock the system with Tux-L, after unlocking the system (after waiting for roughly 30 minutes) gedit moved to the other 100% scaled window and is there in a weird place (see screenshot). How reproducible: Not always, maybe related to the waiting time between locking and unlocking the screen. I will try to figure out if this is related and update this issue with my findings. Steps to Reproduce: 1. Set up a configuration as described. 2. Open gedit maximized on the right display. 3. Lock the system with Tux-L 4. Wait for a relative long time (say 30 minutes) 5. Unlock the screen by typing in the password. Actual results: gedit moved to the left display and is positioned in a wrong way (see screenshot) Expected results: gedit should be in the same display as when the system was locked. Additional info: I do not think that this issue is related to suspending the system, as I could reproduce after fresh boot without having the system suspended. $ inxi -G Graphics: Device-1: AMD Baffin [Radeon RX 460/560D / Pro 450/455/460/555/555X/560/560X] driver: amdgpu v: kernel Display: wayland server: Fedora Project X.org 1.20.8 driver: ati,modesetting unloaded: fbdev,vesa resolution: 1: 1920x1080~60Hz 2: 1680x1050~60Hz OpenGL: renderer: Radeon RX 560 Series (POLARIS11 DRM 3.37.0 5.7.11-200.fc32.x86_64 LLVM 10.0.0) v: 4.6 Mesa 20.1.5
Created attachment 1714638 [details] GNOME display settings
Created attachment 1714639 [details] gedit moved to the other screen and in a wrong position
You can see in the screenshot that it looks like that gedit is aligned at the top of the larger window, but having the size of the smaller window. In reality the bottoms of the windows are aligned, not the tops.
See also: bug 1815492.
See also: https://gitlab.gnome.org/GNOME/mutter/-/issues/1419
See also: https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/1001984
See also: https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/2092 https://bugs.launchpad.net/gnome-shell/+bug/1295267 https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/380 https://github.com/linuxmint/Cinnamon/issues/5487
In GNOME mutter gitlab (https://gitlab.gnome.org/GNOME/mutter/-/issues/1419#note_937356) it was pointed out to me that the incorrect placement of the windows in the monitors happens when the monitors of different size and resolution are aligned at the bottom. When they are aligned at the top, the problem disappears.
This message is a reminder that Fedora 32 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora 32 on 2021-05-25. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '32'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 32 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 32 changed to end-of-life (EOL) status on 2021-05-25. Fedora 32 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.