Some windows placed on other monitor when scale = 200%
Affected version
Provide at least the following information:
- Ubuntu 22.04
- libmutter-10-0 42.0-1ubuntu1
- Occurs on Wayland, did not test Xorg
Bug summary
Some windows (reliably) open on the wrong (secondary) monitor when that monitor has 200% scaling set.
Steps to reproduce
- Have a two-monitor setup (laptop + external here), with secondary left of primary, making the external monitor primary, with workspaces only on primary.
- Set up the secondary (left) monitor with 100% scaling
- Open gedit (or some other gnome app) on the primary monitor
- Open the "Open file" dialog
- Notice it opens on top of the application window as expected
- Change scaling for secondary (left) monitor to 200%.
- Open the "Open file" dialog again
- See that it opens on the wrong monitor.
In my case, the left monitor is 2256x1504, the right monitor is 1600x1200.
This seems to happen on every "File open" dialog (also in evince, pdfarranger) and some applications when starting (at least pdfarranger) and every time reliably. Other applications seem reliably unaffected (gnome-settings, include the keyboard shortcuts popup, gnome-extension-tweaks, foot terminal).
Putting the primary monitor left of the secondary does not show the problem (i.e. the leftmost monitor must be scaled, probably because there is some problem with global coordinates, which are calculated left-to-right of course). Making the left (scaled) monitor primary still shows the problem, but less severe (the popup is mostly on the correct right monitor, and only partially on the left monitor).
What is also interesting is that if the dialog is open and you change the scale from 200% to 100%, the dialog moves into the correct position. But once it is in the correct position, it stays put, even when changing the scale to 200% again.
What happened
What did you expect to happen
Relevant logs, screenshots, screencasts etc.
This same issue seems to have been experienced by @ConfusedPinguin as well, as gathered from this comment (Note that I think the bug report itself might be a different issue, I'm not sure).