SUMMARY Using the keyboard while on the lock screen triggers the "wrong" monitor, which is a monitor that is not set as primary on my Plasma installation. STEPS TO REPRODUCE 1. Lock the screen 2. Press a button on the keyboard 3. The triggered lock screen is not the correct one, independently of pointer location OBSERVED RESULT The lock screen is correctly triggered when tapping on the keyboard, showing the password prompt. However, this happens on a monitor that is not set as primary on Plasma. Changing which monitor is set as primary changes nothing at all, which makes me think that this might be up to some X11 leftover. I can reproduce this same behavior on SDDM (I imagine that this makes sense since afaik monitors on Wayland are handled by KWin?). None of this happens on an X11 session. EXPECTED RESULT I expect the triggered lock screen to either 1. be the one belonging to the primary monitor, or 2. be the one containing the mouse pointer. SOFTWARE/OS VERSIONS Operating System: Fedora Linux 38 KDE Plasma Version: 5.27.8 KDE Frameworks Version: 5.110.0 Qt Version: 5.15.11 Kernel Version: 6.5.9-200.fc38.x86_64 (64-bit) Graphics Platform: Wayland Processors: 12 × AMD Ryzen 5 3600 6-Core Processor Memory: 15.5 GiB of RAM Graphics Processor: AMD Radeon RX 580 Series Manufacturer: Micro-Star International Co., Ltd Product Name: MS-7C02 System Version: 1.0 ADDITIONAL INFORMATION One monitor is an LG Ultragear (set at 144hz) while the other is a Samsung S22B150 (60hz). This only happens on Wayland and I'm not able to reproduce it on X11.
Can reproduce in Plasma 6 too.
Currently kscreenlocker has code to give focus to the UI on the screen with mouse; upstream Qt bug https://bugreports.qt.io/browse/QTBUG-133204 causes the wrong cursor position to be returned.