Bug 499980 - Lockscreen no longer locks the screen
Summary: Lockscreen no longer locks the screen
Status: RESOLVED WORKSFORME
Alias: None
Product: plasmashell
Classification: Plasma
Component: Screen locking (other bugs)
Version First Reported In: 6.3.0
Platform: Fedora RPMs Linux
: NOR grave
Target Milestone: 1.0
Assignee: Plasma Bugs List
URL:
Keywords: regression
Depends on:
Blocks:
 
Reported: 2025-02-13 12:36 UTC by janick
Modified: 2025-04-13 03:46 UTC (History)
4 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description janick 2025-02-13 12:36:06 UTC
SUMMARY
The KDE lockscreen no longer lock the screen, while idle or when I lock the screen manually since Plasma 6.3. I get a blackscreen for a half second, then my unlocked desktop.

STEPS TO REPRODUCE
1. deactivate/activate the lock screen
2. Changed parameters like "when is the passoword required" or the time to activate the screen

OBSERVED RESULT
No changes :(

SOFTWARE/OS VERSIONS
Fedora 41
Kernel:  6.12.11-200.fc41.x86_64 (64-bit)
KDE Plasma Version: 6.3.0
KDE Frameworks Version: 6.10.0
Qt Version: 6.8.2
running on Wayland

ADDITIONAL INFORMATION
I have a GTX 1060 with proprietary NVIDIA drivers loaded from the Fedora RPM Fusion Non Free Repo. Never had problems with it. The bug is new with KDE 6.3
Comment 1 John 2025-02-13 14:34:21 UTC
I cannot reproduce on Debian (unstable repository) with an Intel integrated GPU (UHD 620).
Comment 2 Nate Graham 2025-02-19 15:32:14 UTC
Does it happen in a new clean user account?

If you switch to using the Nouveau drivers on your main user account, does it still happen?
Comment 3 janick 2025-02-19 16:02:07 UTC
(In reply to Nate Graham from comment #2)
> Does it happen in a new clean user account?
> 
> If you switch to using the Nouveau drivers on your main user account, does
> it still happen?


I cannot switch to a new user account while clicking on "switch user" with nvidia and also nouveau loaded. I get a blackscreen with my no movable cursor. I activated the auto-login via command line months ago, maybe thats the reason, I never used two users on this device before.

On my main user account with nouveaou loaded and nvidia blacklisted the screen-lock bug also happens.
Comment 4 David Redondo 2025-02-20 07:40:59 UTC
> . I activated the auto-login via command line months ago

How did you do that?
Comment 5 janick 2025-02-22 10:59:57 UTC
(In reply to David Redondo from comment #4)
> > . I activated the auto-login via command line months ago
> 
> How did you do that?

I added the "User" and "Session" parameters in /etc/sddm.conf under "[Autologin]" months ago. Now I wanted to check again and the parameters are... gone? But in KDE System Settings autologin is still enabled. If I am correctly informed, KDE overwrites this setting again when I change something in the GUI. Maybe thats the reason for the missing parameters I added, but I think you know it better. All I can say is, that Autologin is enabled via System Settings, not over terminal anymore, sorry for the misinformation
Comment 6 Nate Graham 2025-02-24 13:38:30 UTC
Auto-login is not related to screen locking, JFYI.
Comment 7 John Kizer 2025-03-14 05:41:17 UTC
Hi - just a thought, are there any messages about kscreenlocker_greet recorded in the system journal when you try locking the screen? Are any crashes perhaps showing up in the results of the command `coredumpctl list --reverse` from when that happens?
Comment 8 Bug Janitor Service 2025-03-29 03:46:57 UTC
๐Ÿ›๐Ÿงน โš ๏ธ This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information, then set the bug status to REPORTED. If there is no change for at least 30 days, it will be automatically closed as RESOLVED WORKSFORME.

For more information about our bug triaging procedures, please read https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging.

Thank you for helping us make KDE software even better for everyone!
Comment 9 Bug Janitor Service 2025-04-13 03:46:57 UTC
๐Ÿ›๐Ÿงน This bug has been in NEEDSINFO status with no change for at least 30 days. Closing as RESOLVED WORKSFORME.