Update snapshot 20240918 causing "screen locker is broken"problem

After a lot of experimentation, I have some interesting news.

For me, uninstalling pam_pkcs11 makes the issue go away, even when using the latest “broken” pam version 1.6.1-4.1.
Can anyone confirm this?

Edit: Don’t forget locking pam_pkcs11 after uninstalling, i.e. with
sudo zypper addlock pam_pkcs11
, or else it will be auto-reinstalled with the next update!

3 Likes

Very nice, thanks. Works for me as well!

1 Like

Can confirm, that works too!

2 Likes

Just a quick update:
Fabain Vogt managed to identify the exact problem over on bugzilla.
With that information I was able to make a patch and submitted that:

If all goes well and I didn’t screw up anything in the sumbit request, an official patch for pam_pkcs11 should be available in a few days.

4 Likes

Final Update: The bug should be resolved with openSUSE Tumbleweed 20240926 / pam_pkcs11 0.6.12-7.1.

3 Likes

Yep, seems fixed for me!

2 Likes

This same screenlocker problem came to bite me in Slowroll. Is this patch pending in such distribution?

It’s announced, so on the mirrors.

2 Likes

I’ll keep an eye on those channels, thank you :slight_smile:

I have the same issue on Tumbleweed. After locking screen or choosing sleep to RAM. I have to reboot as a result. It happens both on X11 and Wayland.

Please don’t necro threads. There is almost 30 days between the last post and yours so unless you haven’t updated in the past month you are not experiencing the same problem.

And if you haven’t updated in the past month, do so because this problem is solved.

but the thing is I did update all the files and issue still persists. In fact when I installed opensuse tumbleweed 12 days ago for the first time and there was this problem from the start. Even after doing all necessary system updates and reinstalling the two aforementioned files

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.