You are not logged in.

#1 Yesterday 16:24:33

D@rkmind
Member
From: London
Registered: 2011-10-26
Posts: 10

Can't get past SDDM after recent upgrade

I updated all my machines to the latest version this morning. All went well except one laptop. Suddenly SDDM fails to loads the style and shows the error message:

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

file:///usr/share/sddm/themes/breeze/Main.qml: module "1" is not installed

In case I type the password and proceed, KDE loads into a blank screen and the only thing that work is the right-click menu. Though opening any dialog windows from that menu result into the app crash.

I've checked the entire FS for *.pacnew files - there're none. I tried to compare the list of packages with the other machines (that work), I can't see any difference.

I've tried re-installing packages like breeze, sddm and any packages that have them in their name.

What else can I do to troubleshoot it?

Last edited by D@rkmind (Yesterday 16:56:47)

Online

#2 Today 19:57:58

arcum42
Member
Registered: 2019-07-07
Posts: 1

Re: Can't get past SDDM after recent upgrade

Try running fc-cache -rs . If it gives you a core dump, run sudo fc-cache -rsv , and try to get an idea what font it's having trouble with, and uninstall it.

I recently had to uninstall ttf-google-fonts-git due to fontconfig having all sorts of problems with one of the fonts in it, and sddm not loading was one of the issues this caused.

(Bear in mind if this is the problem, you may have to go around changing fonts on things, or installing alternate packages to get the fonts you need. ttf-google-fonts-typewolf seemed like a decent alternative to ttf-google-fonts-git.)

Offline

#3 Today 21:48:31

D@rkmind
Member
From: London
Registered: 2011-10-26
Posts: 10

Re: Can't get past SDDM after recent upgrade

I've just tried running both commands - they didn't show any failure or errors.

I also checked what font-related packages are installed in the system. Both working and problematic machines have exactly the same list:

adobe-source-code-pro-fonts
adwaita-fonts
cantarell-fonts
fontconfig
gnu-free-fonts
gsfonts
lib32-fontconfig
libfontenc
libxfont2
noto-fonts
noto-fonts-emoji
python-fonttools
xorg-fonts-encodings

The original error looks quite strange. It's like there's a bug in the source code and it failed to substitute "%1", so instead of the actual module name that it can't load, it's printing just "1"...

Online

Board footer

Powered by FluxBB