this post was submitted on 02 Nov 2024
26 points (100.0% liked)

Linux

48287 readers
657 users here now

From Wikipedia, the free encyclopedia

Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).

Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.

Rules

Related Communities

Community icon by Alpár-Etele Méder, licensed under CC BY 3.0

founded 5 years ago
MODERATORS
 

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
top 8 comments
sorted by: hot top controversial new old
[–] eldavi@lemmy.ml 6 points 2 weeks ago

Yum has the ability to search for and install plugins like that with yum provides and yum whatprovides and I'd be surprised if Suse didn't port it or create something similar.

[–] Ephera@lemmy.ml 4 points 2 weeks ago (1 children)

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...

[–] qaz@lemmy.world 1 points 2 weeks ago (1 children)

That's what I've been doing for the past 2 days

[–] Ephera@lemmy.ml 7 points 2 weeks ago (1 children)

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 rollback and 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

[–] qaz@lemmy.world 4 points 2 weeks ago* (last edited 2 weeks ago)

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 😅.

[–] JRepin@lemmy.ml 4 points 2 weeks ago

Install pam_pkcs11 package, which contains the missing library

[–] JRepin@mstdn.io 0 points 2 weeks ago (1 children)

@qaz Install pam_pkcs11 package, which contains the missing library

[–] qaz@lemmy.world 2 points 2 weeks ago* (last edited 2 weeks ago)

Thanks! I'll try that

EDIT: It did not help, I'll look into it tomorrow