Skip to main content ↑ ↓
Topic: Total Lockout of Computer After 07.05.2023 Updates. (Read 835 times) previous topic - next topic
0 Members and 3 Guests are viewing this topic.

Total Lockout of Computer After 07.05.2023 Updates.

FAIL.

After todays updates its not possible to login into KDE/Plasma (SDDM and runit). Complete lockout.

So here are the errors at the SDDM Login Screen (password is OK at ctrl+alt+Fx):

"The current theme cannot be loaded due to the errors below, please select other theme.
file:///urs/share/sddm/themes/breeze/Main.qml:12:1:plugin cannot be loaded for module "org.kde.plasma.core".
Cannot load library /usr/lib/qt/qml/org/kde/plasma/core/libcorebindingsplugin.so (libplist-2.0.so.3: cannot open shared object file: No such file or directory).

TOTAL LOCK-OUT OF THE SYSTEM. Its just a theme so it shouldn't be an issue and one shouldn't be totally locked out of the system, right? Not to mention no breeze updates or anything like that today.

So about "no such file or directroy":
$ sudo find / -name libcorebindingsplugin.so ------> gives positive resault. its in: /usr/lib/qt/qml/org/kde/plasma/core/libcorebindingsplugin.so

So maybe some ".so" bindings, I don't know. And why suddenly. Shouldn't pacman take care of it? So anyway, I run:
$ [root] ldconfig  <----- should take care of it, right? Nope. No, still total lockout.

So maybe libplist messed it up? I downgraded. Nope. No luck. Still total lockout of my KDE/Plasma/Configs/Yamls/rc-s....

Breeze broken maybe? But why would it be? $ pacman -S breeze-whatever. Nope! Still locked out!

Oh, lets look at the "experts" from these arch(based) distros and do some searx instance search. They talk about some "git packages versions. Let's check: $ pacman -Qs git. Nope no luck there either. Still totally locked out.FAIL.


Freebsd same issue and lockout. Marked as solved. Nope! There's no "solved" ANYWHERE in the post. I'm still locked out.


Lets check runit and SDDM, but wait. The sddm login shows up (albeit no breeze), so what gives? Let's check anyway
$ ls /run/runit/service/, hmmm, no luck. SDDM is there, no surprise. But just to be sure:
$ sv up blah blah start stop blah blah. No luck. Still locked out.

How about logs:
FAIL.

After todays updates its not possible to login into KDE/Plasma (SDDM and runit). Complete lockout.

So here are the errors at the SDDM Login Screen (password is OK at ctrl+alt+Fx):

"The current theme cannot be loaded due to the errors below, please select other theme.
file:///urs/share/sddm/themes/breeze/Main.qml:12:1:plugin cannot be loaded for module "org.kde.plasma.core".
Cannot load library /usr/lib/qt/qml/org/kde/plasma/core/libcorebindingsplugin.so (libplist-2.0.so.3: cannot open shared object file: No such file or directory).

TOTAL LOCK-OUT OF THE SYSTEM. Its just a theme so it shouldn't be an issue and one shouldn't be totally locked out of the system, right? Not to mention no breeze updates or anything like that today.

So about "no such file or directroy":
$ sudo find / -name libcorebindingsplugin.so ------> gives positive resault. its in: /usr/lib/qt/qml/org/kde/plasma/core/libcorebindingsplugin.so

So maybe some ".so" bindings, I don't know. And why suddenly. Shouldn't pacman take care of it? So anyway, I run:
$ [root] ldconfig  <----- should take care of it, right? Nope. No, still total lockout.

So maybe libplist messed it up? I downgraded. Nope. No luck. Still total lockout of my KDE/Plasma/Configs/Yamls/rc-s....

Breeze broken maybe? But why would it be? $ pacman -S breeze-whatever. Nope! Still locked out!

Oh, lets look at the "experts" from these arch(based) distros and do some searx instance search. They talk about some "git packages versions. Let's check: $ pacman -Qs git. Nope no luck there either. Still totally locked out.FAIL.

After todays updates its not possible to login into KDE/Plasma (SDDM and runit). Complete lockout.

So here are the errors at the SDDM Login Screen (password is OK at ctrl+alt+Fx):

"The current theme cannot be loaded due to the errors below, please select other theme.
file:///urs/share/sddm/themes/breeze/Main.qml:12:1:plugin cannot be loaded for module "org.kde.plasma.core".
Cannot load library /usr/lib/qt/qml/org/kde/plasma/core/libcorebindingsplugin.so (libplist-2.0.so.3: cannot open shared object file: No such file or directory).

TOTAL LOCK-OUT OF THE SYSTEM. Its just a theme so it shouldn't be an issue and one shouldn't be totally locked out of the system, right? Not to mention no breeze updates or anything like that today.

So about "no such file or directroy":
$ sudo find / -name libcorebindingsplugin.so ------> gives positive resault. its in: /usr/lib/qt/qml/org/kde/plasma/core/libcorebindingsplugin.so

So maybe some ".so" bindings, I don't know. And why suddenly. Shouldn't pacman take care of it? So anyway, I run:
$ [root] ldconfig  <----- should take care of it, right? Nope. No, still total lockout.

So maybe libplist messed it up? I downgraded. Nope. No luck. Still total lockout of my KDE/Plasma/Configs/Yamls/rc-s....

Breeze broken maybe? But why would it be? $ pacman -S breeze-whatever. Nope! Still locked out!

Oh, lets look at the "experts" from these arch(based) distros and some searx instance search. They talk about some "git packages versions. Let's check: $ pacman -Qs git. Nope no luck there either. Still totally locked out.

Freebsd same issue and lockout. Marked as solved. Nope! There's no "solved" ANYWHERE in the post. I'm still locked out.


Lets check runit and SDDM, but wait. The sddm login shows up (albeit no breeze), so what gives? Let's check anyway
$ ls /run/runit/service/, hmmm, no luck. SDDM is there, no surprise. But just to be sure:
$ sv up blah blah start stop blah blah. No luck. Still locked out.


[2023-05-06T11:01:11+0200] [ALPM] upgraded less (1:608-2 -> 1:633-1)
[2023-05-06T11:01:11+0200] [ALPM] upgraded onetbb (2021.8.0-3 -> 2021.8.0-3.1)
[2023-05-06T11:01:11+0200] [ALPM] upgraded whois (5.5.16-1 -> 5.5.17-1)
[2023-05-06T11:01:11+0200] [ALPM] upgraded xz (5.4.2-1 -> 5.4.3-1)
[2023-05-06T11:01:12+0200] [ALPM] transaction completed

[2023-05-06T11:01:11+0200] [ALPM] upgraded less (1:608-2 -> 1:633-1)
[2023-05-06T11:01:11+0200] [ALPM] upgraded onetbb (2021.8.0-3 -> 2021.8.0-3.1)
[2023-05-06T11:01:11+0200] [ALPM] upgraded whois (5.5.16-1 -> 5.5.17-1)
[2023-05-06T11:01:11+0200] [ALPM] upgraded xz (5.4.2-1 -> 5.4.3-1)
[2023-05-06T11:01:12+0200] [ALPM] transaction completed

[2023-05-06T11:01:11+0200] [ALPM] upgraded less (1:608-2 -> 1:633-1)
[2023-05-06T11:01:11+0200] [ALPM] upgraded onetbb (2021.8.0-3 -> 2021.8.0-3.1)
[2023-05-06T11:01:11+0200] [ALPM] upgraded whois (5.5.16-1 -> 5.5.17-1)
[2023-05-06T11:01:11+0200] [ALPM] upgraded xz (5.4.2-1 -> 5.4.3-1)
[2023-05-06T11:01:12+0200] [ALPM] transaction completed

Event this:
[2023-05-07T15:13:33+0200] [PACMAN] Running 'pacman -S libcorebindings'
[2023-05-07T15:16:22+0200] [PACMAN] Running 'pacman -S breeze'
[2023-05-07T15:16:32+0200] [ALPM] transaction started
[2023-05-07T15:16:32+0200] [ALPM] reinstalled breeze (5.27.4-1)
[2023-05-07T15:16:32+0200] [ALPM] transaction completed
[2023-05-07T15:16:32+0200] [ALPM] running 'gtk-update-icon-cache.hook'...
[2023-05-07T15:16:32+0200] [ALPM] running 'update-desktop-database.hook'...
[2023-05-07T15:17:52+0200] [PACMAN] Running 'pacman -S sddm-runit'
[2023-05-07T15:17:54+0200] [ALPM] transaction started
[2023-05-07T15:17:54+0200] [ALPM] reinstalled sddm-runit (20211029-1)
[2023-05-07T15:17:54+0200] [ALPM] transaction completed
[2023-05-07T15:17:54+0200] [ALPM] running 'runit-install.hook'...
[2023-05-07T15:17:54+0200] [ALPM-SCRIPTLET]    ==> Add a service:
[2023-05-07T15:17:54+0200] [ALPM-SCRIPTLET]    ln -s /etc/runit/sv/<service> /run/runit/service/
[2023-05-07T15:17:54+0200] [ALPM-SCRIPTLET]    ==> Start/stop/restart a service:
[2023-05-07T15:17:54+0200] [ALPM-SCRIPTLET]    sv <start/stop/restart> <service>

[2023-05-07T17:16:02+0200] [PACMAN] Running 'pacman -S plasma-meta'
[2023-05-07T17:16:21+0200] [ALPM] transaction started
[2023-05-07T17:16:21+0200] [ALPM] installed oxygen (5.27.4-1)
[2023-05-07T17:16:21+0200] [ALPM] installed plasma-disks (5.27.4-1)
[2023-05-07T17:16:21+0200] [ALPM] installed plasma-firewall (5.27.4-1)
[2023-05-07T17:16:21+0200] [ALPM] installed plasma-workspace-wallpapers (5.27.4.1-1)
[2023-05-07T17:16:21+0200] [ALPM] installed plasma-systemmonitor (5.27.4-1)
[2023-05-07T17:16:21+0200] [ALPM] installed bolt (0.9.5-1)
[2023-05-07T17:16:21+0200] [ALPM] installed plasma-thunderbolt (5.27.4-1)
[2023-05-07T17:16:21+0200] [ALPM] installed plasma-vault (5.27.4.1-1)
[2023-05-07T17:16:21+0200] [ALPM] installed plasma-welcome (5.27.4.1-1)
[2023-05-07T17:16:21+0200] [ALPM] installed archlinux-appstream-data (20230421-1)
[2023-05-07T17:16:21+0200] [ALPM] installed qt5-webview (5.15.9-1.1)
[2023-05-07T17:16:21+0200] [ALPM] installed discover (5.27.4-1)
[2023-05-07T17:16:21+0200] [ALPM] installed plasma-meta (5.27-3)
[2023-05-07T17:16:22+0200] [ALPM] transaction completed
[2023-05-07T17:16:22+0200] [ALPM] running '30-udev-reload.hook'...
[2023-05-07T17:16:22+0200] [ALPM] running '90-update-appstream-cache.hook'...
[2023-05-07T17:16:23+0200] [ALPM-SCRIPTLET] ✔ Metadata cache was updated successfully.
[2023-05-07T17:16:23+0200] [ALPM] running 'gtk-update-icon-cache.hook'...
[2023-05-07T17:16:23+0200] [ALPM] running 'update-desktop-database.hook'...
[2023-05-07T17:16:37+0200] [PACMAN] Running 'pacman -S plasma theme'
[2023-05-07T17:18:33+0200] [PACMAN] Running 'pacman -S world/breeze'
[2023-05-07T17:18:35+0200] [ALPM] transaction started
[2023-05-07T17:18:35+0200] [ALPM] reinstalled breeze (5.27.4-1)
[2023-05-07T17:18:35+0200] [ALPM] transaction completed
[2023-05-07T17:18:35+0200] [ALPM] running 'gtk-update-icon-cache.hook'...
[2023-05-07T17:18:35+0200] [ALPM] running 'update-desktop-database.hook'...
[2023-05-07T17:20:40+0200] [PACMAN] Running 'pacman -Rns libplist'
[2023-05-07T17:20:47+0200] [PACMAN] Running 'pacman -S libplist'
[2023-05-07T17:20:48+0200] [ALPM] transaction started
[2023-05-07T17:20:48+0200] [ALPM] reinstalled libplist (2.3.0-1)
[2023-05-07T17:20:48+0200] [ALPM] transaction completed

Nope. No luck. Still locked out. Total FAIL. Any idea?

Maybe SDDM Logs (a "few last ones")?:

17:12:21.953] (II) DAEMON: Greeter starting...
[17:12:21.962] (II) HELPER: [PAM] Starting...
[17:12:21.962] (II) HELPER: [PAM] Authenticating...
[17:12:21.962] (II) HELPER: [PAM] returning.
[17:12:21.999] (II) DAEMON: Greeter session started successfully
[17:12:22.049] (II) DAEMON: Message received from greeter: Connect
[17:18:43.982] (WW) DAEMON: Signal received: SIGTERM
[17:18:43.983] (II) DAEMON: Greeter stopping...
[17:18:43.983] (II) DAEMON: Socket server stopping...
[17:18:43.983] (II) DAEMON: Socket server stopped.
[17:18:43.983] (II) DAEMON: Display server stopping...
[17:18:43.998] (II) DAEMON: Display server stopped.
[17:18:43.998] (II) DAEMON: Running display stop script  "/usr/share/sddm/scripts/Xstop"
[17:18:44.006] (II) DAEMON: Greeter stopping...
[17:18:44.006] (WW) DAEMON: QProcess: Destroyed while process ("/usr/lib/sddm/sddm-helper") is still running.
[17:19:07.888] (II) DAEMON: Initializing...
[17:19:07.895] (II) DAEMON: Starting...
[17:19:07.895] (II) DAEMON: Logind interface found
[17:19:07.896] (II) DAEMON: Adding new display on vt 7 ...
[17:19:07.899] (II) DAEMON: Loading theme configuration from ""
[17:19:07.899] (II) DAEMON: Display server starting...
[17:19:07.899] (II) DAEMON: Adding cookie to "/var/run/sddm/{a6bd6848-3fa7-410f-9532-24732e7c05dc}"
[17:19:07.912] (II) DAEMON: Running: /usr/bin/X -nolisten tcp -background none -seat seat0 vt7 -auth /var/run/sddm/{a6bd6848-3fa7-410f-9532-24732e7c05dc} -noreset -displayfd 17
[17:19:08.687] (II) DAEMON: Setting default cursor
[17:19:08.695] (II) DAEMON: Running display setup script  "/usr/share/sddm/scripts/Xsetup"
[17:19:08.698] (II) DAEMON: Display server started.
[17:19:08.698] (II) DAEMON: Socket server starting...
[17:19:08.698] (II) DAEMON: Socket server started.
[17:19:08.700] (II) DAEMON: Loading theme configuration from "/usr/share/sddm/themes/breeze/theme.conf"
[17:19:08.701] (II) DAEMON: Greeter starting...
[17:19:08.717] (II) HELPER: [PAM] Starting...
[17:19:08.717] (II) HELPER: [PAM] Authenticating...
[17:19:08.717] (II) HELPER: [PAM] returning.
[17:19:08.747] (II) DAEMON: Greeter session started successfully
[17:19:08.893] (II) DAEMON: Message received from greeter: Connect
[17:19:12.947] (II) DAEMON: Message received from greeter: Login
[17:19:12.947] (II) DAEMON: Reading from "/usr/share/xsessions/plasma.desktop"
[17:19:12.947] (II) DAEMON: Reading from "/usr/share/xsessions/plasma.desktop"
[17:19:12.948] (II) DAEMON: Session "/usr/share/xsessions/plasma.desktop" selected, command: "dbus-run-session /usr/bin/startplasma-x11"
[17:19:12.995] (II) HELPER: [PAM] Starting...
[17:19:12.995] (II) HELPER: [PAM] Authenticating...
[17:19:12.996] (II) HELPER: [PAM] Preparing to converse...
[17:19:12.996] (II) HELPER: [PAM] Conversation with 1 messages
[17:19:13.010] (II) HELPER: [PAM] returning.
[17:19:13.011] (II) DAEMON: Authenticated successfully
[17:19:13.075] (II) HELPER: [PAM] Closing session
[17:19:13.078] (II) HELPER: [PAM] Ended.
[17:19:13.079] (II) DAEMON: Auth: sddm-helper exited successfully
[17:19:13.079] (II) DAEMON: Greeter stopped.
[17:19:13.117] (II) HELPER: Starting: "/usr/share/sddm/scripts/Xsession \"dbus-run-session /usr/bin/startplasma-x11\""
[17:19:13.119] (II) HELPER: Adding cookie to "/home/freedom/.Xauthority"
[17:19:13.124] (II) DAEMON: Session started
[17:19:13.178] (II) HELPER: [PAM] Closing session
[17:19:13.179] (II) HELPER: [PAM] Ended.
[17:19:13.180] (WW) DAEMON: Auth: sddm-helper exited with 127
[17:19:13.180] (II) DAEMON: Socket server stopping...
[17:19:13.180] (II) DAEMON: Socket server stopped.
[17:19:13.180] (II) DAEMON: Display server stopping...
[17:19:13.460] (II) DAEMON: Display server stopped.
[17:19:13.460] (II) DAEMON: Running display stop script  "/usr/share/sddm/scripts/Xstop"
[17:19:13.468] (II) DAEMON: Removing display ":0" ...
[17:19:13.468] (II) DAEMON: Adding new display on vt 7 ...
[17:19:13.469] (II) DAEMON: Loading theme configuration from ""
[17:19:13.469] (II) DAEMON: Display server starting...
[17:19:13.469] (II) DAEMON: Adding cookie to "/var/run/sddm/{fac8eae2-2587-4530-8d34-29b6497def71}"
[17:19:13.487] (II) DAEMON: Running: /usr/bin/X -nolisten tcp -background none -seat seat0 vt7 -auth /var/run/sddm/{fac8eae2-2587-4530-8d34-29b6497def71} -noreset -displayfd 18
[17:19:13.918] (II) DAEMON: Setting default cursor
[17:19:13.922] (II) DAEMON: Running display setup script  "/usr/share/sddm/scripts/Xsetup"
[17:19:13.924] (II) DAEMON: Display server started.
[17:19:13.924] (II) DAEMON: Socket server starting...
[17:19:13.924] (II) DAEMON: Socket server started.
[17:19:13.924] (II) DAEMON: Loading theme configuration from "/usr/share/sddm/themes/breeze/theme.conf"
[17:19:13.924] (II) DAEMON: Greeter starting...
[17:19:13.933] (II) HELPER: [PAM] Starting...
[17:19:13.933] (II) HELPER: [PAM] Authenticating...
[17:19:13.933] (II) HELPER: [PAM] returning.
[17:19:13.984] (II) DAEMON: Greeter session started successfully
[17:19:14.035] (II) DAEMON: Message received from greeter: Connect
[17:21:29.018] (WW) DAEMON: Signal received: SIGTERM
[17:21:29.019] (II) DAEMON: Greeter stopping...
[17:21:29.019] (II) DAEMON: Socket server stopping...
[17:21:29.019] (II) DAEMON: Socket server stopped.
[17:21:29.019] (II) DAEMON: Display server stopping...
[17:21:29.043] (II) DAEMON: Display server stopped.
[17:21:29.043] (II) DAEMON: Running display stop script  "/usr/share/sddm/scripts/Xstop"
[17:21:29.046] (II) DAEMON: Greeter stopping...
[17:21:29.046] (WW) DAEMON: QProcess: Destroyed while process ("/usr/lib/sddm/sddm-helper") is still running.
[17:21:45.860] (II) DAEMON: Initializing...
[17:21:45.867] (II) DAEMON: Starting...
[17:21:45.867] (II) DAEMON: Logind interface found
[17:21:45.868] (II) DAEMON: Adding new display on vt 7 ...
[17:21:45.871] (II) DAEMON: Loading theme configuration from ""
[17:21:45.871] (II) DAEMON: Display server starting...
[17:21:45.871] (II) DAEMON: Adding cookie to "/var/run/sddm/{44d90525-f12d-4d2f-bf29-b73ceca98f4c}"
[17:21:45.878] (II) DAEMON: Running: /usr/bin/X -nolisten tcp -background none -seat seat0 vt7 -auth /var/run/sddm/{44d90525-f12d-4d2f-bf29-b73ceca98f4c} -noreset -displayfd 17
[17:21:46.666] (II) DAEMON: Setting default cursor
[17:21:46.679] (II) DAEMON: Running display setup script  "/usr/share/sddm/scripts/Xsetup"
[17:21:46.681] (II) DAEMON: Display server started.
[17:21:46.681] (II) DAEMON: Socket server starting...
[17:21:46.682] (II) DAEMON: Socket server started.
[17:21:46.683] (II) DAEMON: Loading theme configuration from "/usr/share/sddm/themes/breeze/theme.conf"
[17:21:46.684] (II) DAEMON: Greeter starting...
[17:21:46.700] (II) HELPER: [PAM] Starting...
[17:21:46.700] (II) HELPER: [PAM] Authenticating...
[17:21:46.700] (II) HELPER: [PAM] returning.
[17:21:46.732] (II) DAEMON: Greeter session started successfully
[17:21:46.914] (II) DAEMON: Message received from greeter: Connect
[17:21:51.093] (II) DAEMON: Message received from greeter: Login
[17:21:51.094] (II) DAEMON: Reading from "/usr/share/xsessions/plasma.desktop"
[17:21:51.094] (II) DAEMON: Reading from "/usr/share/xsessions/plasma.desktop"
[17:21:51.094] (II) DAEMON: Session "/usr/share/xsessions/plasma.desktop" selected, command: "dbus-run-session /usr/bin/startplasma-x11"
[17:21:51.113] (II) HELPER: [PAM] Starting...
[17:21:51.113] (II) HELPER: [PAM] Authenticating...
[17:21:51.113] (II) HELPER: [PAM] Preparing to converse...
[17:21:51.113] (II) HELPER: [PAM] Conversation with 1 messages
[17:21:51.120] (II) HELPER: [PAM] returning.
[17:21:51.121] (II) DAEMON: Authenticated successfully
[17:21:51.169] (II) HELPER: [PAM] Closing session
[17:21:51.170] (II) HELPER: [PAM] Ended.
[17:21:51.171] (II) DAEMON: Auth: sddm-helper exited successfully
[17:21:51.172] (II) DAEMON: Greeter stopped.
[17:21:51.199] (II) HELPER: Starting: "/usr/share/sddm/scripts/Xsession \"dbus-run-session /usr/bin/startplasma-x11\""
[17:21:51.201] (II) HELPER: Adding cookie to "/home/freedom/.Xauthority"
[17:21:51.206] (II) DAEMON: Session started
[17:21:51.276] (II) HELPER: [PAM] Closing session
[17:21:51.279] (II) HELPER: [PAM] Ended.
[17:21:51.281] (WW) DAEMON: Auth: sddm-helper exited with 127
[17:21:51.281] (II) DAEMON: Socket server stopping...
[17:21:51.281] (II) DAEMON: Socket server stopped.
[17:21:51.281] (II) DAEMON: Display server stopping...
[17:21:51.532] (II) DAEMON: Display server stopped.
[17:21:51.532] (II) DAEMON: Running display stop script  "/usr/share/sddm/scripts/Xstop"
[17:21:51.543] (II) DAEMON: Removing display ":0" ...
[17:21:51.544] (II) DAEMON: Adding new display on vt 7 ...
[17:21:51.544] (II) DAEMON: Loading theme configuration from ""
[17:21:51.544] (II) DAEMON: Display server starting...
[17:21:51.544] (II) DAEMON: Adding cookie to "/var/run/sddm/{e4bb3c99-b0de-49f9-a06d-40e71a519070}"
[17:21:51.561] (II) DAEMON: Running: /usr/bin/X -nolisten tcp -background none -seat seat0 vt7 -auth /var/run/sddm/{e4bb3c99-b0de-49f9-a06d-40e71a519070} -noreset -displayfd 18
[17:21:51.981] (II) DAEMON: Setting default cursor
[17:21:51.985] (II) DAEMON: Running display setup script  "/usr/share/sddm/scripts/Xsetup"
[17:21:51.987] (II) DAEMON: Display server started.
[17:21:51.987] (II) DAEMON: Socket server starting...
[17:21:51.987] (II) DAEMON: Socket server started.
[17:21:51.987] (II) DAEMON: Loading theme configuration from "/usr/share/sddm/themes/breeze/theme.conf"
[17:21:51.987] (II) DAEMON: Greeter starting...
[17:21:51.996] (II) HELPER: [PAM] Starting...
[17:21:51.996] (II) HELPER: [PAM] Authenticating...
[17:21:51.996] (II) HELPER: [PAM] returning.
[17:21:52.018] (II) DAEMON: Greeter session started successfully
[17:21:52.060] (II) DAEMON: Message received from greeter: Connect
[17:21:55.721] (II) DAEMON: Message received from greeter: Login
[17:21:55.721] (II) DAEMON: Reading from "/usr/share/xsessions/plasma.desktop"
[17:21:55.721] (II) DAEMON: Reading from "/usr/share/xsessions/plasma.desktop"
[17:21:55.722] (II) DAEMON: Session "/usr/share/xsessions/plasma.desktop" selected, command: "dbus-run-session /usr/bin/startplasma-x11"
[17:21:55.736] (II) HELPER: [PAM] Starting...
[17:21:55.736] (II) HELPER: [PAM] Authenticating...
[17:21:55.736] (II) HELPER: [PAM] Preparing to converse...
[17:21:55.736] (II) HELPER: [PAM] Conversation with 1 messages
[17:21:55.743] (II) HELPER: [PAM] returning.
[17:21:55.743] (II) DAEMON: Authenticated successfully
[17:21:55.779] (II) HELPER: [PAM] Closing session
[17:21:55.780] (II) HELPER: [PAM] Ended.
[17:21:55.780] (II) DAEMON: Auth: sddm-helper exited successfully
[17:21:55.780] (II) DAEMON: Greeter stopped.
[17:21:55.810] (II) HELPER: Starting: "/usr/share/sddm/scripts/Xsession \"dbus-run-session /usr/bin/startplasma-x11\""
[17:21:55.811] (II) HELPER: Adding cookie to "/home/freedom/.Xauthority"
[17:21:55.815] (II) DAEMON: Session started
[17:21:55.837] (II) HELPER: [PAM] Closing session
[17:21:55.839] (II) HELPER: [PAM] Ended.
[17:21:55.840] (WW) DAEMON: Auth: sddm-helper exited with 127
[17:21:55.840] (II) DAEMON: Socket server stopping...
[17:21:55.840] (II) DAEMON: Socket server stopped.
[17:21:55.840] (II) DAEMON: Display server stopping...
[17:21:56.121] (II) DAEMON: Display server stopped.
[17:21:56.121] (II) DAEMON: Running display stop script  "/usr/share/sddm/scripts/Xstop"
[17:21:56.132] (II) DAEMON: Removing display ":0" ...
[17:21:56.133] (II) DAEMON: Adding new display on vt 7 ...
[17:21:56.133] (II) DAEMON: Loading theme configuration from ""
[17:21:56.134] (II) DAEMON: Display server starting...
[17:21:56.134] (II) DAEMON: Adding cookie to "/var/run/sddm/{c5e04d0e-4cd6-4bf4-952d-29e76e235010}"
[17:21:56.150] (II) DAEMON: Running: /usr/bin/X -nolisten tcp -background none -seat seat0 vt7 -auth /var/run/sddm/{c5e04d0e-4cd6-4bf4-952d-29e76e235010} -noreset -displayfd 18
[17:21:56.529] (II) DAEMON: Setting default cursor
[17:21:56.532] (II) DAEMON: Running display setup script  "/usr/share/sddm/scripts/Xsetup"
[17:21:56.534] (II) DAEMON: Display server started.
[17:21:56.534] (II) DAEMON: Socket server starting...
[17:21:56.534] (II) DAEMON: Socket server started.
[17:21:56.534] (II) DAEMON: Loading theme configuration from "/usr/share/sddm/themes/breeze/theme.conf"
[17:21:56.535] (II) DAEMON: Greeter starting...
[17:21:56.544] (II) HELPER: [PAM] Starting...
[17:21:56.544] (II) HELPER: [PAM] Authenticating...
[17:21:56.544] (II) HELPER: [PAM] returning.
[17:21:56.571] (II) DAEMON: Greeter session started successfully
[17:21:56.610] (II) DAEMON: Message received from greeter: Connect
[17:22:35.273] (II) DAEMON: Message received from greeter: Reboot
[17:22:36.366] (WW) DAEMON: Signal received: SIGTERM
[17:22:36.366] (II) DAEMON: Greeter stopping...
[17:22:36.366] (II) DAEMON: Socket server stopping...
[17:22:36.366] (II) DAEMON: Socket server stopped.
[17:22:36.366] (II) DAEMON: Display server stopping...
[17:22:36.400] (II) HELPER: [PAM] Closing session
[17:22:36.400] (WW) HELPER: [PAM] closeSession: Error in service module
[17:22:36.401] (II) HELPER: [PAM] Ended.
[17:22:36.616] (II) DAEMON: Display server stopped.
[17:22:36.616] (II) DAEMON: Running display stop script  "/usr/share/sddm/scripts/Xstop"
[17:22:36.623] (II) DAEMON: Greeter stopping...
[17:22:36.624] (WW) DAEMON: QProcess: Destroyed while process ("/usr/lib/sddm/sddm-helper") is still running.

Any idea? Did you change something in config after updates?

User log? Nope. Just some two lines of x11 pulseaudio crap. Nothing there.

Messages log? Probably not related at all but got somwhere bunch of these from dbus:

dbus-daemon[1091]: [session uid=1000 pid=1089] Reloaded configuration
May  7 14:48:49 xxxx dbus-daemon[1031]: [session uid=979 pid=1029] Reloaded configuration
May  7 14:48:49 xxxx dbus-daemon[1031]: Unable to set up transient service directory: XDG_RUNTIME_DIR "/run/user/979" not available: No such file or directory
May  7 14:48:49 xxxx dbus-daemon[1031]: [session uid=979 pid=1029] Reloaded configuration
....

And some "errors.log":
May  7 14:54:46 xxxx login[875]: pam_elogind(login:session): Failed to connect to system bus: No such file or directory
May  7 14:56:46 xxxx elogind[917]: elogind is already running as PID 890
May  7 14:57:52 xxxx sddm-helper[1169]: pam_elogind(sddm-greeter:session): Failed to connect to system bus: No such file or directory
May  7 14:58:05 xxxx elogind[922]: elogind is already running as PID 911
May  7 14:59:19 xxxx sddm-helper[1076]: pam_elogind(sddm-greeter:session): Failed to connect to system bus: No such file or directory
May  7 15:12:10 xxxx sddm-helper[1084]: pam_elogind(sddm-greeter:session): Failed to connect to system bus: No such file or directory
May  7 15:12:24 xxxx elogind[923]: elogind is already running as PID 912
May  7 15:30:00 xxxx login[885]: pam_elogind(login:session): Failed to connect to system bus: No such file or directory
May  7 15:30:22 xxxx elogind[918]: elogind is already running as PID 905
May  7 15:31:06 xxxx elogind[918]: elogind is already running as PID 907
May  7 15:35:50 xxxx elogind[932]: elogind is already running as PID 921
May  7 15:36:19 xxxx sddm-helper[1082]: pam_elogind(sddm-greeter:session): Failed to connect to system bus: No such file or directory
May  7 16:33:09 xxxx elogind[912]: elogind is already running as PID 885
May  7 16:36:26 xxxx elogind[925]: elogind is already running as PID 904
May  7 17:03:17 xxxx elogind[930]: elogind is already running as PID 919
May  7 17:03:28 xxxx sddm-helper[1084]: pam_elogind(sddm-greeter:session): Failed to connect to system bus: No such file or directory
May  7 17:07:24 xxxx elogind[927]: elogind is already running as PID 916
May  7 17:08:34 xxxx elogind[923]: elogind is already running as PID 911
May  7 17:08:59 xxxx sddm-helper[1077]: pam_elogind(sddm-greeter:session): Failed to connect to system bus: No such file or directory
May  7 17:12:01 xxxx elogind[927]: elogind is already running as PID 915
May  7 17:18:43 xxxx login[887]: pam_elogind(login:session): Failed to connect to system bus: No such file or directory
May  7 17:19:07 xxxx elogind[931]: elogind is already running as PID 919
May  7 17:21:45 xxxx elogind[955]: elogind is already running as PID 946
May  7 17:22:36 xxxx sddm-helper[1126]: pam_elogind(sddm-greeter:session): Failed to connect to system bus: No such file or directory

WHY I AM SUDDENLY LOCKED OUT OF MY "COMPUTA"?


 

Re: Total Lockout of Computer After 07.05.2023 Updates. Major FAIL after 3 years.

Reply #1 –
It's caused by a library error: libplist updated but KDE software is still looking for the older library version.

I'm not sure if this is the smartest way of doing things but making a temporary symbolic link by running
Code: [Select]
sudo ln -s /usr/lib/libplist-2.0.so /usr/lib/libplist-2.0.so.3
(followed by a reboot) should get things working again for now.

Note that SDDM may not reinherit the previous theme, meaning you'll need to manually set it in KDE's system settings again.

Re: Total Lockout of Computer After 07.05.2023 Updates. Major FAIL after 3 years.

Reply #2 –
Quote from: Teru – on
It's caused by a library error: libplist updated but KDE software is still looking for the older library version.

I'm not sure if this is the smartest way of doing things but making a temporary symbolic link by running
Code: [Select]
sudo ln -s /usr/lib/libplist-2.0.so /usr/lib/libplist-2.0.so.3
(followed by a reboot) should get things working again for now.

Note that SDDM may not reinherit the previous theme, meaning you'll need to manually set it in KDE's system settings again.


Creating symlink from one to another worked. Logged in and got "KDE Greeter" as if I was strating a brand new install. Evererything is there. Settings of SDDM/Themes too. But the question is. Shouldn't this be fixed upstream (at Atix level?). Its just a workaround. Its the second at least library to be fixed or blocked or downgraded or symlinked. Just after non-working LibreOffice/liborcus/etc.

So how it will be solved upstream. What after another update of KDE. Should I remove they symlink? What would be the command to fix it another time after KDE update (will happen very soon as usual).

So with another update will it point to the new library and I will be locked again?

Re: Total Lockout of Computer After 07.05.2023 Updates. Major FAIL after 3 years.

Reply #3 –
I'm only a basic user myself so I can't answer most of your questions. Once this is resolved you should probably remove the symlink however as it will be redundant.
As for future updates, the best advice I can give is to take note of any root error you may encounter (in this case it would have been the "libplist-2.0.so.3: cannot open shared object file" line).

Re: Total Lockout of Computer After 07.05.2023 Updates.

Reply #4 –
I use Dolphin under XFCE.
Yesterday, I couldn't launch Dolphin anymore because of this same library.
After updating kio-extras everything is back to normal.

Re: Total Lockout of Computer After 07.05.2023 Updates.

Reply #5 –
Quote from: tintin – on
I use Dolphin under XFCE.
Yesterday, I couldn't launch Dolphin anymore because of this same library.
After updating kio-extras everything is back to normal.
Can confirm that this update resolved the core issue.

For those who made use of the temporary fix above, once updated you can remove the unnecessary symlink by running:
Code: [Select]
sudo rm /usr/lib/libplist-2.0.so.3
Please do be sure to confirm that you got the 'kio-extras' update before doing this however, otherwise you will run into the issue again.