I’ve attached a literal screen shot of all systemd errors. It seems to be caused by kscreenlocker_greet because of a missing shared object file. The boot 9 hours ago was from a read-only snapshot, and therefore doesn’t have it.
I have already tried updating with zypper dup, but that did not help.
Error as text:
PAM unable to dlopen(/usr/lib64/security/pam_pkcs11.so): /usr/lib64/security/pam_pkcs11.so: cannot open shared object file: No such file or directory
Can’t you roll back to a snapshot before the update that broke it? Then you can wait with updating for a week or two, in hopes that it gets fixed in the next Tumbleweed update…
That’s what I’ve been doing for the past 2 days
Oh, you don’t have to always boot anew from the read-only snapshot.
When you’re booted into the working read-only snapshot, run
sudo snapper rollbackand then do a normal reboot.This will make that read-only snapshot your new (read-writable) system state. So, after doing this, your OS will be as if you never applied that update.
More info on that command: https://doc.opensuse.org/documentation/leap/archive/15.0/reference/html/book.opensuse.reference/cha.snapper.html#sec.snapper.snapshot-boot
Oh, that makes sense.
I tried it, and ran it in the latest broken snapshot and was surprised why it didn’t roll back to a previous version 😅.
EDIT: It appears that didn’t work and instead overrode my working snapshot.
EDIT 2: Yep, it’s gone. I only have snapshots of me trying to fix it by updating.