[CLOSED] Recent system updates prevent SDDM from working properlyl

cloverskull · 2021-12-14 22:08:31

Hey friends, not sure where this goes, so posting here. I’m at a bit of a loss what to do. I guess I’ll summarize this in terms of the order of events I observed which led to my current broken state.

First off, recently, yay was complaining about a bunch of missing python2 packages. This is something I assumed was just due to the deprecation of python2, and this also seemed rather innocuous and I don’t think it has any impact on the current issues - I’m merely mentioning this for completeness.

Now, after an upgrade and a reboot in the past 24ish hours, I noticed that informant was broken, and the rest of my OS was blocked on upgrading any further since the dependency on informant working correctly was failing. I uninstalled informant, and then was able to further upgrade my OS.

There were dozens of complaints of python 3.10 packages being ignored by the current interpreter. This was…alarming. /usr/bin/python was pointing at /usr/bin/python3, which was pointing at python 3.9.

I have no recollection of manually installing python 3.10, and as far as I know, I’d only ever really installed the mainline pacman python packages, and not the AUR packages.

I tried manually reinstalling pip and manually installing missing packages, but now I’ve gotten myself into a state where I can’t launch KDE. SDDM complains about broken things (I will need to take a photo and downdraft the text of the error later) and my entire OS is in a state of broken. All I can do is boot to a tty at this point.

Anyone know what happened here? How should I go about fixing this? Is it recoverable?

Thanks. I’m fairly distraught and appreciate the help.

EDIT -- I blew away everything and reinstalled from scratch. Having backups of my user home directory is a benefit! I know this isn't really the arch way, but I need this computer to work right now for business reasons and didn't have the time to troubleshoot and figure things out the right way.

Last edited by cloverskull (2021-12-14 23:51:34)

AndroGR · 2021-12-14 22:10:51

cloverskull wrote:

Hey friends, not sure where this goes, so posting here. I’m at a bit of a loss what to do. I guess I’ll summarize this in terms of the order of events I observed which led to my current broken state.
First off, recently, yay was complaining about a bunch of missing python2 packages. This is something I assumed was just due to the deprecation of python2, and this also seemed rather innocuous and I don’t think it has any impact on the current issues - I’m merely mentioning this for completeness.
Now, after an upgrade and a reboot in the past 24ish hours, I noticed that informant was broken, and the rest of my OS was blocked on upgrading any further since the dependency on informant working correctly was failing. I uninstalled informant, and then was able to further upgrade my OS.
There were dozens of complaints of python 3.10 packages being ignored by the current interpreter. This was…alarming. /usr/bin/python was pointing at /usr/bin/python3, which was pointing at python 3.9.
I have no recollection of manually installing python 3.10, and as far as I know, I’d only ever really installed the mainline pacman python packages, and not the AUR packages.
I tried manually reinstalling pip and manually installing missing packages, but now I’ve gotten myself into a state where I can’t launch KDE. SDDM complains about broken things (I will need to take a photo and downdraft the text of the error later) and my entire OS is in a state of broken. All I can do is boot to a tty at this point.
Anyone know what happened here? How should I go about fixing this? Is it recoverable?
Thanks. I’m fairly distraught and appreciate the help.

Always include the package names. Python libraries are many, but it only takes some malicious code to break your system.

jasonwryan · 2021-12-14 22:13:35

Change your title to a less hysterical one, your OS isn't bricked, you just can't lauch your graphical environment.

And then post some actual logs, related to that issue.

cloverskull · 2021-12-14 22:41:31

Fair enough re: hysterical. Had to cancel a job interview because of this, so suffice it to say, I was feeling rather hysterical at the time.

I don’t seem to have any python 3.10 binaries anywhere, so I’m really puzzled why the reference to the python3.10 directories existed in the first place.

I did the following to rebuild all packages dependent on python 3.9 and 3.10:

yay -S $(pacman -Qoq /usr/lib/python3.9) —answerclean All
yay -S $(pacman -Qoq /usr/lib/python3.10) -answerclean All

This got rid of all the errors about my current interpreter, however my issues launching SDDM remain. There are some other problems, like cpupower-gui-git not working automatically at boot (evidently it depends on ‘dbus’ which I can’t seem to install via pip).

SDDM spits out the following error and I am unable to login:

The current theme cannot be loaded due to the errors below, please select another theme.

file:///usr/share/sddm/themesbreeze/Main.qml:14:1: plugin cannot be loaded for module “org.kde.plasma.core”: Cannot load library /usr/lib/qt/qml/org/kde/plasma/core/libcorebindingsplugin.so: (/usr/lib/libKF5GuiAddons.so.5: undefined symbol: wl)proxy)marshal)flags)

jasonwryan · 2021-12-14 22:54:20

┌─[Centurion ~]
└─╼ pacman -F /usr/lib/libKF5GuiAddons.so.5
usr/lib/libKF5GuiAddons.so.5 is owned by extra/kguiaddons 5.46.0-1
┌─[Centurion ~]
└─╼ pkgsearch kguiaddons
kguiaddons 5.89.0-1 extra

Arch Linux

#1 2021-12-14 22:08:31

[CLOSED] Recent system updates prevent SDDM from working properlyl

#2 2021-12-14 22:10:51

Re: [CLOSED] Recent system updates prevent SDDM from working properlyl

#3 2021-12-14 22:13:35

Re: [CLOSED] Recent system updates prevent SDDM from working properlyl

#4 2021-12-14 22:41:31

Re: [CLOSED] Recent system updates prevent SDDM from working properlyl

#5 2021-12-14 22:54:20

Re: [CLOSED] Recent system updates prevent SDDM from working properlyl

Board footer