Linux

48719 readers

895 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

Posts must be relevant to operating systems running the Linux kernel. GNU/Linux or otherwise.
No misinformation
No NSFW content
No hate speech, bigotry, etc

Related Communities

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

founded 5 years ago

MODERATORS

AgreeableLandscape@lemmy.ml

nooter692@lemmy.ml

MarcellusDrum@lemmy.ml

cypherpunks@lemmy.ml

cyclohexane@lemmy.ml

d3Xt3r@lemmy.nz

kscreenlocker_greet broke with a recent update of OpenSUSE (November 1). Any advice on how to fix it? (lemmy.world)

submitted 1 month ago* (last edited 1 month ago) by qaz@lemmy.world to c/linux@lemmy.ml

8 comments fedilink hide all child comments

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

you are viewing a single comment's thread
view the rest of the comments

[–] Ephera@lemmy.ml 7 points 1 month 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 1 month ago* (last edited 1 month 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 😅.