https://bugs.kde.org/show_bug.cgi?id=437520
--- Comment #7 from l...@protonmail.com --- Can confirm. I've looked into this further, and managed to find a way to reliably reproduce it without having to wait for sleep. It's definitely an issue with multiple monitors, with the external monitor going to sleep/disconnecting. Symptoms are the exact same as in the OP, mouse can move, but login screen never reacts to input and keeps showing the clock only. The clock is frozen at the time the issue started (same time as in journalctl (see below)). However, after further testing I've found that the login form actually is there, just invisible. If you hover over the right area with the cursor, you get the textinput caret, and if you click and enter your password, you can actually unlock the system. STEPS TO REPRODUCE 1. Connect external monitor (in my case, the machine is a laptop, and the external monitor is connected via HDMI). 2. Set screen setup to external monitor only. 3. Lock system. 4. Disconnect external monitor. Either physically disconnecting the HDMI cable or turning off the monitor's power switch works. 5. Wait for the internal monitor to turn on. 6. Reconnect the external monitor. OBSERVED RESULT The described situation happens, screen locker graphical output appears frozen, only clock is displayed, cursor still moves and responds to text input fields, unlock is possible if the text input field is focused. EXPECTED RESULT Normal graphical output from screen unlocker as on a single monitor. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Kubuntu 22.04 (available in About System) KDE Plasma Version: 5.24.4 KDE Frameworks Version: 5.92.0 Qt Version: 5.15.3 Graphics Platform: X11 ADDITIONAL INFORMATION Possible workarounds are: - As mentioned, finding the invisible password input field and entering the password blindly works. - Dropping to shell, running `loginctl unlock-sessions` works. - Dropping to shell, running `killall kwin_x11` works (but restarting kwin once unlocked is a nuisance). In addition, journalctl reproducibly displays information related to EDID when the disconnect & reconnect is performed. I have attached the logs. Nothing else is logged during the relevant time period. -- You are receiving this mail because: You are watching all bug changes.
