Bug 454820 - Using hot keys, I get output that the screenlocker is broken and instructions on how to unlock from a virtual terminal
Summary: Using hot keys, I get output that the screenlocker is broken and instructions...
Status: RESOLVED DOWNSTREAM
Alias: None
Product: kscreenlocker
Classification: Unmaintained
Component: general (other bugs)
Version First Reported In: 5.24.90
Platform: openSUSE Linux
: NOR normal
Target Milestone: ---
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2022-06-04 03:58 UTC by Ronnie Bailey
Modified: 2022-11-05 02:20 UTC (History)
3 users (show)

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

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Ronnie Bailey 2022-06-04 03:58:12 UTC 
SUMMARY
The summary states the problem. If I use hot keys to lock the screen, I get the error. However if I click on kscreenlocker_greeter from Dolphin, it works normally. dmesg gives me the following, with the second line repeated many times: 
Lockdown: X: raw io port access is restricted; see man kernel_lockdown.7
Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7

OS is openSUSE 15.3, using their newer KDE repos. I use X11 and do not have Wayland installed. KERNAL_LOCKDOWN is a new kernel feature, but I am not sure why it would prevent locking from hot keys, but allow it by opening the greeter with a mouse click. 

STEPS TO REPRODUCE
1. Use the hot keys to initiate the screenlocker
2. 
3. 

OBSERVED RESULT
Given a SDDM screen stating that the screenlocker is broken and instructions on how to unlock with a virtual terminal

EXPECTED RESULT
I expect to have the lockscreen presented after using the hot keys

SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma: openSUSE 15.3 kernel-default-5.3.18
(available in About System)
KDE Plasma Version: 5.24.90
KDE Frameworks Version: 5.24.90
Qt Version: 5.15.2

ADDITIONAL INFORMATION
Comment 1 Nate Graham 2022-06-06 18:01:07 UTC 
This was broken in the beta, but fixed since then, and will be fixed in the final 5.25 release. Thanks for testing!
Comment 2 Ronnie Bailey 2022-06-06 18:30:33 UTC 
(In reply to Nate Graham from comment #1)
> This was broken in the beta, but fixed since then, and will be fixed in the
> final 5.25 release. Thanks for testing!

Thank you for the info. Since openSUSE doesn't list these as unstable or testing, I had no idea. They are actually listed as stable, with unstable or testing packages at different URLs. Hopefully the 5.25 packages will be available soon in those repos.
Comment 3 Ronnie Bailey 2022-06-14 23:32:25 UTC 
I upgraded all KDE and Plasma packages today. I can confirm that this bug still exists in kscreenlocker-5.25 as I now have 5 broken machines.
Comment 4 Nate Graham 2022-11-04 21:33:40 UTC 
Is it better now with 5.26 and newer openSUSE packages? Nobody else has been reporting this, so I'm wondering if it's weird interaction between your repos' software.
Comment 5 Ronnie Bailey 2022-11-05 02:03:14 UTC 
(In reply to Nate Graham from comment #4)
> Is it better now with 5.26 and newer openSUSE packages? Nobody else has been
> reporting this, so I'm wondering if it's weird interaction between your
> repos' software.

Yes. Apologies for not reporting earlier.
Comment 6 Nate Graham 2022-11-05 02:20:21 UTC 
Awesome, thanks.