Hello
I hop someone can help repair this. I was doing update, and the updates failed, with an error similar to ’ updates interrupted, no changes’, but it appears something changed, as my system would not do anything anymore
on reboot, I have errors about themes missing on the login screen, and it looks different. I am pretty sure this is the pertinent part of the logs:
Jan 15 11:28:12 linux-f5tb sddm-greeter[3246]: Reading from "/usr/share/xsessions/plasma5.desktop"
Jan 15 11:28:12 linux-f5tb sddm-greeter[3246]: inotify_add_watch("/usr/share/wayland-sessions") failed: "No such file or directory"
Jan 15 11:28:12 linux-f5tb sddm-greeter[3246]: Connected to the daemon.
Jan 15 11:28:12 linux-f5tb sddm[1621]: Message received from greeter: Connect
Jan 15 11:28:12 linux-f5tb sddm-greeter[3246]: Loading file:///usr/share/sddm/themes/breeze-openSUSE/Main.qml...
Jan 15 11:28:12 linux-f5tb sddm-greeter[3246]: file:///usr/share/sddm/themes/breeze-openSUSE/Main.qml:25:1: plugin cannot be loaded for module "org.kde.plasma.core": Cannot load library /usr/lib64/qt5/qml/org/kde/plasma/core/libcorebindingsplugin.so: (libpulsecommon-9.0.so: cannot open shared object file: No such f
import org.kde.plasma.core 2.0 as PlasmaCore
^
Jan 15 11:28:12 linux-f5tb sddm-greeter[3246]: file:///usr/share/sddm/themes/breeze-openSUSE/Main.qml:25:1: plugin cannot be loaded for module "org.kde.plasma.core": Cannot load library /usr/lib64/qt5/qml/org/kde/plasma/core/libcorebindingsplugin.so: (libpulsecommon-9.0.so: cannot open shared object file: No such f
import org.kde.plasma.core 2.0 as PlasmaCore
^
Jan 15 11:28:12 linux-f5tb sddm-greeter[3246]: Fallback to embedded theme
Jan 15 11:28:12 linux-f5tb sddm-greeter[3246]: Adding view for "DVI-0" QRect(0,0 2048x1152)
Jan 15 11:28:12 linux-f5tb sddm-greeter[3246]: Loading file:///usr/share/sddm/themes/breeze-openSUSE/Main.qml...
Jan 15 11:28:12 linux-f5tb sddm-greeter[3246]: file:///usr/share/sddm/themes/breeze-openSUSE/Main.qml:25:1: plugin cannot be loaded for module "org.kde.plasma.core": Cannot load library /usr/lib64/qt5/qml/org/kde/plasma/core/libcorebindingsplugin.so: (libpulsecommon-9.0.so: cannot open shared object file: No such f
import org.kde.plasma.core 2.0 as PlasmaCore
^
Jan 15 11:28:12 linux-f5tb sddm-greeter[3246]: file:///usr/share/sddm/themes/breeze-openSUSE/Main.qml:25:1: plugin cannot be loaded for module "org.kde.plasma.core": Cannot load library /usr/lib64/qt5/qml/org/kde/plasma/core/libcorebindingsplugin.so: (libpulsecommon-9.0.so: cannot open shared object file: No such f
import org.kde.plasma.core 2.0 as PlasmaCore
^
Jan 15 11:28:12 linux-f5tb sddm-greeter[3246]: Fallback to embedded theme
Jan 15 11:28:12 linux-f5tb sddm-greeter[3246]: Adding view for "VGA-0" QRect(2048,0 1920x1080)
Jan 15 11:28:12 linux-f5tb systemd[3240]: Started D-Bus User Message Bus.
Jan 15 11:28:12 linux-f5tb sddm-greeter[3246]: Message received from daemon: Capabilities
Jan 15 11:28:12 linux-f5tb sddm-greeter[3246]: Message received from daemon: HostName
Jan 15 11:28:20 linux-f5tb systemd-logind[1103]: Removed session 7.
Jan 15 11:28:33 linux-f5tb kernel: SFW2-INext-DROP-DEFLT IN=enp5s0 OUT= MAC=d0:50:99:99:2f:ab:cc:6d:a0:c7:fa:82:08:00 SRC=192.168.1.131 DST=192.168.1.134 LEN=244 TOS=0x00 PREC=0x00 TTL=64 ID=0 DF PROTO=UDP SPT=1900 DPT=53385 LEN=224
can someone suggest a maner to which repair it? thanks John kilbert
The same occurred with my systems this morning. I did as suggested…logged in with ICEWM and ran the updates from a terminal there and all rebooted just fine. Glad to know it wasn’t just me. Happened with two computers here for me.
Well, the desktop’s update applet (or PackageKit for that matter, which the applet is just a frontend for) is not really designed to do “distribution upgrades” as each new Tumbleweed snapshot basically is.
It should work most of the time, but some Tumbleweed upgrades may require manual intervention with zypper (depending on the changes).
And even “zypper up” (which basically is what PackageKit does) may have problems on Tumbleweed (depending on what updates/upgrades there are).
So throw out zypper too?
And no, this is unrelated to the update applet, the same would happen when using zypper too.
Is this a bug concerning dependencies?
I doubt that.
AFAICS, pulseaudio 9.99 does require libpulsecommon-9.99.so.
As mentioned, the likely reason is that the update was aborted somewhere in the middle, when libpulse was already updated but pulseaudio itself not yet.
How braindead is that to serve an update to a graphical updater that will 100% kill the machine? My trust in TW is really dwindling these days…
One of my machines never really recovered from that and the GUI freezes always after some minutes/hours (KDE, clock stops, no new apps to be started or terminated, no shutdown). Really, really bad service quality.
And insulting the people that work for you for free isn’t really helping either…
Btw, AIUI this is actually a longer standing bug in the dbus package.
It restarts the dbus daemon on updates, which it shouldn’t do as it can break many things (including systemd) in the running system.
Of course there are not often updates to dbus, so this was not noticed (or forgotten).
One of my machines never really recovered from that and the GUI freezes always after some minutes/hours (KDE, clock stops, no new apps to be started or terminated, no shutdown). Really, really bad service quality.
Sounds like a different issue. That dbus update only affects the running system, everything should work fine again after a reboot (unless you have incompatible packages installed because the update has been interrupted…)
