[kscreenlocker] [Bug 449857] Lockscreen window sometimes does not get focus by default on X11

Nathan bugzilla_noreply at kde.org
Wed Mar 16 14:41:03 GMT 2022


https://bugs.kde.org/show_bug.cgi?id=449857

--- Comment #47 from Nathan <pokemaster0x01+kde.bugtracking at gmail.com> ---
Comparing the older files on my desktop with the newer ones on my laptop that
display the bug, I believe I have found the source of the problem. Between the
two, looking at the changes to /usr/share/plasma/look-and-feel/, the only
changes other than metadata.{desktop,json} localization changes were in
/usr/share/plasma/look-and-feel/org.kde.breeze.desktop/contents/lockscreen/LockScreenUi.qml,
which added the lines below. Reverting to the old file from my desktop fixed
the bug  (i.e. removing the lines setting visible and enabled), and I can now
enter text on the lock screen without having to hit tab a few times and/or
moving the mouse.


    ---
/usr/share/plasma/look-and-feel/org.kde.breeze.desktop/contents/lockscreen/LockScreenUi.qml-old
    +++
/usr/share/plasma/look-and-feel/org.kde.breeze.desktop/contents/lockscreen/LockScreenUi.qml-new
    @@ -227,6 +227,12 @@
                height: lockScreenRoot.height + units.gridUnit * 3
                focus: true //StackView is an implicit focus scope, so we need
to give this focus so the item inside will have it

    +            // this isn't implicit, otherwise items still get processed
for the scenegraph
    +            visible: opacity > 0
    +            // changing enabled will toggle if an item can have
activeFocus, which otherwise
    +            //keeps the text cursor blinking even when invisble
    +            enabled: visible
    +
                initialItem: MainBlock {
                    id: mainBlock
                    lockScreenUiVisible: lockScreenRoot.uiVisible


My laptop (as it's not the most recent version of Plasma, so it could be
different now):
Linux/KDE Plasma: Kubuntu 20.04
KDE Plasma Version: 5.18.8
KDE Frameworks Version: 5.68.0
Qt Version: 5.12.8

-- 
You are receiving this mail because:
You are the assignee for the bug.


More information about the Visual-design mailing list