https://bugs.kde.org/show_bug.cgi?id=506468
Bug ID: 506468
Summary: Clicks pass through wayland windows to xwayland
windows
Classification: Plasma
Product: kwin
Version First 6.4.1
Reported In:
Platform: Arch Linux
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: xwayland
Assignee: [email protected]
Reporter: [email protected]
Target Milestone: ---
SUMMARY
Mouse clicks inconsistently get passed through from a native wayland window to
an xwayland window positioned behind it when attempting to focus the native
wayland window.
STEPS TO REPRODUCE
1. Open a native wayland window (firefox, kde system settings, dolphin, etc).
2. Open an xwayland window (steam, vscode, godot, discord, etc, or just force
x11).
3. Open a tertiary window, ideally this should be on a secondary monitor, and
also be an xwayland window, again maximized
4. Position the xwayland window anywhere on one monitor. I have noticed it is
more consistent if maximized.
5. Position the wayland window anywhere on the same monitor that the xwayland
window is on. Again, seemingly more consistent if maximized.
6. Ensure the wayland window is in front of the xwayland window
7. Click on the tertiary window so that it's focused
8. Click on the wayland window.
OBSERVED RESULT
The wayland window should show signs of being focused for a fraction of a
second (e.g. decorations n such lighting up), but then the xwayland window
behind it will grab focus, usually interacting with a part of the window that
was clicked such as moving the caret if it's a text editor for example.
Depending on the window, it might be brought to the front visually, or it will
stay behind the wayland window. Either way, if you hold Alt+Tab, you will see
that the window order has updated to reflect the fact that the xwayland window
is focused now, with the next window in the order being the wayland window you
clicked, then the tertiary window.
EXPECTED RESULT
The wayland window will be focused and no weird behavior occurs.
SOFTWARE/OS VERSIONS
OS: Arch Linux
Linux Kernel: 6.15.4-arch2-1 (64-bit)
KDE Plasma Version: 6.4.1
KDE Frameworks Version: 6.15.0
Qt Version: 6.9.1
GPU: NVIDIA GeForce RTX 3060
Graphics Driver: nvidia-open 575.64-5
Window Protocol: wayland
ADDITIONAL INFORMATION
I am unsure if this bug is a multi-monitor issue or not. I recommend
replicating with more than one monitor first both since I am experiencing this
on my system with 2 monitors, and because it just gives more space for a
tertiary window. I have been able to get the described bug to happen regardless
of a window being maximized or not, but from my experimentation it is most
consistent with the following conditions: a maximized vscode window (using the
"code" package from the official arch linux repos), a maximized firefox window
in front of it, and anything as a tertiary window, but on a second monitor. I
have also noticed that this most commonly happens when I have another xwayland
window maximized on my other monitor, although I am like 90% certain that I
have gotten it to happen without this being the case. Additionally, I have
attached a video of the bug occurring.
--
You are receiving this mail because:
You are watching all bug changes.
