Bug: Mutter: Window placement doesn't follow user input on multi-monitor touchscreens
Master ticket gnome-shell#3011
Affected version
Ubuntu 20.04 Mutter 3.36.3 XOrg YES Issue occurs Wayland NO Windows are placed correctly But Wayland doesn't allow remote support so unable to use Wayland.
Bug summary
Use case Point of Sale system with opposing monitors with the cashier side being a touchscreen with no mouse or keyboard. When end user presses the button to initiate a payment Mutter places the window on the customer display where no input is available. A remote support call is necessary in order to move the window back to the input area of the touchscreen.
Previous versions of Mutter didn't exhibit this behavior and workarounds like devilspie are now ignored in the 3.36.3 release of mutter.
Steps to reproduce
- Install a fresh copy of Ubuntu 20.04 LTS on a computer with one Touchscreen and one non-touch.
- Install Chromispos (the open source Point of Sale that we use)
- Click on a product
- Press the = bar on the touchpad
- On Xorg the Payment pop-up where the cashier chooses the payment type like Cash or Card the window will appear on the second screen where there is no access. 5a. On Wayland it pops up just under the = bar
What happened
Mutter placed a window requesting user input on a monitor where no user input is available
Tried as workarounds:
- Devilspie Used to work in older versions of mutter. Now there has to be a click on the window before mutter will give it to devilspie to move. Which completely defeats the purpose.
- Devilspie2 Never has worked on any system, ever.
- Auto Move Windows https://extensions.gnome.org/extension/16/auto-move-windows/ Is ignored by mutter
- Dconf center windows Is an easter egg that places the window between the two montiors. or is just ignored.
What did you expect to happen
The expectation is that the window follows the tap/click. Where the user taps/clicks the window shall open. That the window with user input never open in areas without user input available.
Please see the master ticket for a more detailed description. gnome-shell#3011
Relevant logs, screenshots, screencasts etc.
Thank you for having a look at this bug.