https://bugs.kde.org/show_bug.cgi?id=506468
--- Comment #4 from koni <[email protected]> --- (In reply to Vlad Zahorodnii from comment #3) > Did you change any options in `Legacy X11 App Support`? THIS IS IT OH MY GOD i COMPLETELY forgot that I messed with those settings when starting up my system, it seems I turned on the "Additionally include mouse buttons" checkbox. This appears to be the root cause of the issue, as disabling it makes it stop happening. This solves my issue however i would still consider this to be a bug with that feature in particular. I have also discovered some more information about what makes the bug consistent to perform, here is an updated reproduction list: - Navigate to Legacy X11 App Support settings - Set "Additionally include mouse buttons" to be checked, and apply changes - Open two xwayland windows, position one on one monitor (monitor A), and one on another (monitor B) - Open one native wayland window, position it on one of the two monitors (in this example assume it is on monitor A) - Maximize the xwayland window on monitor B - Maximize the xwayland window on monitor A - Maximize the native wayland window on monitor A - Ensure the native wayland window is above the xwayland window that is on monitor A in the window order, such that the native wayland window appears above the xwayland window - Click onto the xwayland window on monitor B - Click onto the native wayland window on monitor A - Repeat until bug occurs, sometimes it happens and other times it does not, it usually does though. I have had inconsistent results with it working if i simply drag the window borders to fill the screen as opposed to clicking the maximize button, sometimes it causes the bug to occur and other times it doesn't. the most consistent way is to simply maximize all windows. -- You are receiving this mail because: You are watching all bug changes.
