sway: Multiple Xwayland windows are stacked in the wrong order
Sway Version:
- Sway version:
1.10-dev-88b2abf5 (Feb 11 2024, branch 'master') - wlroots version:
0.18.0-dev - OS:
Arch Linux x86_64 - Kernel:
6.7.4-arch1-1
Screencast, Debug Log:
- Screencast:
https://github.com/swaywm/sway/assets/102382754/6aed8b7a-2c98-4b6a-99f8-6d352a942392
- sway debug log: https://paste.rs/IBnpw
- Console log of Chromium run: https://paste.rs/JgwkO
Configuration File:
/etc/sway/config
Description: Reproduction procedure
sudo pacman -S chromium reaperto Install Chromium and REAPERsway -c /etc/sway/config -d 2> sway-run-default_date +%Y%m%d-%H%M%S.logto start Swaymeta+enterto start footchromium<enter>to start Chromiummeta+wto make tab layoutmeta+enterto start footreaper<enter>to start REAPERescapeto close the floating window- click anywhere in the REAPER window
-> I can’t click on the REAPER window, the Chromium tab turns red. Layers are in the wrong order.
Comment
I have heard that REAPER uses some sort of proprietary GUI library for games, so this may be related to that.- The GUI for REAPER was open source. It appears to use this. https://github.com/justinfrankel/WDL
The same problem occurs with Renoise, which is also an application for music and uses its own GUI library often used for games.- I checked again and it did not occur. It seems that since Renoise is also an Xwayland window like Chromium, this phenomenon occurs when used with REAPER at the same time.
- This is a multi-display environment.
Related Links
About this issue
- Original URL
- State: closed
- Created 3 years ago
- Reactions: 1
- Comments: 41 (16 by maintainers)
Commits related to this issue
- desktop/xwayland: don't restack when marking window as inactive daaec72ac01f ("desktop/xwayland: restack surface upon activation") has updated Sway for wlroots commit bfc69decdd04 ("xwm: do not resta... — committed to emersion/sway by emersion 2 years ago
- desktop/xwayland: don't restack when marking window as inactive daaec72ac01f ("desktop/xwayland: restack surface upon activation") has updated Sway for wlroots commit bfc69decdd04 ("xwm: do not resta... — committed to swaywm/sway by emersion 2 years ago
This should be fully fixed with a combination of https://gitlab.freedesktop.org/wlroots/wlroots/-/merge_requests/4756 and this sway patch:
Thank you for all your patience and quickness to respond! Thank you for making open source better.
I found out how to reproduce the event in the current version.
Version:
Reproduction procedure:
This will still reproduce, but a quick operation of the following will reproduce it again.
Screenshot:
Screencast:
https://github.com/swaywm/sway/assets/102382754/7412337c-75e9-4bf3-999c-a535960844e6
20240216-141721-chromium.log
sway-run-default_20240216-140729.log
Nothing changes. See between 16 and 24 seconds of the above screencast.
The incorrect stacking condition will be resolved and normalized. See between 28 and 50 seconds of the above screencast.