SUMMARY After updating to plasma 5.24, the screen lock program (from Ctrl + Alt + L) oftentimes will not show the password bar even after having pressed some key. When this happens, it is possible to position the mouse there and click it as it will change the cursor towards a blinking line (for writing) and it will take what's written there, but one has to know where it is as it is not visually distinguishable from the background. STEPS TO REPRODUCE 1. Wait a long time until the screen auto locks (doesn't happen when locking it manually, and the bug is not always reproducible, but happens quite often). 2. Press some key. 3. Watch for the password bar. OBSERVED RESULT The password bar is invisible, and if I do manage to find it with the mouse and write, doesn't show any asterisks. EXPECTED RESULT The password bar should always be visible. SOFTWARE/OS VERSIONS Operating System: Debian GNU/Linux KDE Plasma Version: 5.24.3 KDE Frameworks Version: 5.90.0 Qt Version: 5.15.2 Kernel Version: 5.16.0-5-amd64 (64-bit) Graphics Platform: X11 Processors: 16 × AMD Ryzen 7 2700 Eight-Core Processor Memory: 15.6 GiB of RAM Graphics Processor: AMD VEGA10
1. What Plasma theme are you using? 2. Can you share a screenshot of the whole screen? 3. Does the issue reproduce if you run `/usr/libexec/kscreenlocker_greet --testing` in a terminal window? (exact path may vary by distro; you can find the executable's path on your system with `find /usr -name kscreenlocker_greet`)
(In reply to Nate Graham from comment #1) > 1. What Plasma theme are you using? > 2. Can you share a screenshot of the whole screen? > 3. Does the issue reproduce if you run `/usr/libexec/kscreenlocker_greet > --testing` in a terminal window? > > (exact path may vary by distro; you can find the executable's path on your > system with `find /usr -name kscreenlocker_greet`) 1. The global theme is set to "Breeze Dark". Individual components are a mixture of oxygen and custom themes. 2. "Print Screen" doesn't work when the screen is locked. 3. Not reproducible with it, at least not at the first try, but it does show some messages: Locked at 1648364728 file:///usr/share/plasma/look-and-feel/org.kde.breeze.desktop/contents/components/VirtualKeyboard.qml:11:1: Type InputPanel unavailable qrc:/QtQuick/VirtualKeyboard/content/InputPanel.qml:127:5: Type Keyboard unavailable qrc:/QtQuick/VirtualKeyboard/content/components/Keyboard.qml:38:1: module "QtQuick.VirtualKeyboard.Plugins" is not installed file:///usr/share/plasma/look-and-feel/org.kde.breeze.desktop/contents/components/UserList.qml:42:9: Unable to assign [undefined] to bool
Thanks. I believe this is Bug 370676 *** This bug has been marked as a duplicate of bug 370676 ***
I don't think it's the same as Bug 370676 (or at least my bug report closed as a duplicate of Bug 370676). The issue I encountered was, when the lock screen was hidden, pressing Tab caused it to enter an infinite CPU loop and stop responding to all input (even moving mouse and keystrokes). Since in this bug, you can still move the mouse, the cursor changes based on mouse position, and you can type the password, this sounds like a rendering error (possibly a variation of Bug 450301).
*** This bug has been marked as a duplicate of bug 374890 ***
Indeed, I think I mis-triaged this as a duplicate of bug 374890, which was not correct. Sorry about that.
Can you let me know if you still experience the issue in Plasma 5.27? If so, please answer the following questions: - Do you experience this only when you have multiple screens connected, or does it also sometimes happen when there's only one screen? - Does the cursor change to an I-beam when it passes over the invisible password field, or not?
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone!
This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone!