https://bugs.kde.org/show_bug.cgi?id=406800
Bug ID: 406800
Summary: XWayland: bad cursor events after DisplayPort monitor
hotplug
Product: kwin
Version: 5.14.5
Platform: Other
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: wayland-generic
Assignee: [email protected]
Reporter: [email protected]
Target Milestone: ---
SUMMARY
After turning off and on a DisplayPort monitor, there's a region of my *other*
monitor that warps the position of XWayland input events.
My setup
- Left monitor, 2560x1440 DVI (primary monitor)
- Right monitor, 1920x1200 DisplayPort
STEPS TO REPRODUCE
1. Use PC normally in Plasma Wayland session
2. Open an XWayland app (e.g. Chromium, or `QT_QPA_PLATFORM=xcb kate`) on left
monitor, interact with it normally
3. Turn off right-monitor.
- For DisplayPort this causes a hotplug event, all open windows move to the
left monitor, kwin "compositor settings" window pops up
4. Turn on right-monitor.
- Open windows move back
OBSERVED RESULT
Mouse input on all xwayland apps on left monitor is not properly recognized.
- Some input is recognized, but, with a bad relative offset. Or it's only
recognized outside of a 1920x1200 region on the 2560x1440 display
- This includes click events being misdirected to wrong parts of the window, it
affects dragging window, it affects mouse-hover on UI elements etc
EXPECTED RESULT
Expected to still be able to interact with XWayland apps normally
SOFTWARE/OS VERSIONS
Linux: Debian Buster amd64
KDE Plasma Version: 5.14.5
KDE Frameworks Version: 5.54.0
Qt Version: 5.11.3
Xwayland 1.20.4
Radeon RX570 with AMDGPU / Mesa 18.3.4
ADDITIONAL INFORMATION
I originally raised this as an XWayland bug here
https://gitlab.freedesktop.org/xorg/xserver/issues/680
But the issue doesn't happen on GNOME Wayland, and nor on Weston (although that
had a different problem).
So there is some aspect of this bug that is specific to Kwin_wayland.
--
You are receiving this mail because:
You are watching all bug changes.
