https://bugs.kde.org/show_bug.cgi?id=449857
--- Comment #43 from Fabian Vogt <fab...@ritter-vogt.de> --- The cursor not blinking means that the text input is focused, but it doesn't have active focus, most likely because the window isn't focused. I can reproduce the issue in a VM with multihead-QXL (needs virt-viewer instead of virt-manager): 1. Lock the screen with just display 1 active 2. Enable display 2 3. Only one of the lockscreen views has focus (as expected), disable the screen with the focused one 4. The view remains unfocused By connecting to view's activeChanged() signal, it's visible that it never gets focus. Explicitly calling requestActiveFocus after view removal doesn't help either. FWICT, that the lockscreen isn't focused after screen removal is a bug in KWin. I can't reproduce that with kscreenlocker_greet --testing, so it might be in screenlock specific code. No idea about the more general issue reported initially that there's no focus at all. That could've been caused by a packaging issue indeed. -- You are receiving this mail because: You are watching all bug changes.
