Hey guys. Good moment for me to check up on the forums. There's a LOT of things happening in my life at the moment and I have almost no time at all to be online. Less contributing. I won't go into details but this will still be true for another while.
Yesterday I had a pacman update with qt5-base from obcore and the new-config-location sddm version:
marian@ obarun ~ % grep -i upgraded /var/log/pacman.log
[...]
[2020-04-10T22:20:17-0500] [ALPM] upgraded qt5-base (5.14.1-4 -> 5.14.2-2)
[2020-04-10T22:20:18-0500] [ALPM] upgraded polkit (0.116-11 -> 0.116-12)
[2020-04-10T22:20:18-0500] [ALPM] upgraded kscreenlocker (5.18.3-2 -> 5.18.4.1-2)
[2020-04-10T22:20:35-0500] [ALPM] upgraded linux-lts419 (4.19.113-2 -> 4.19.114-3)
[2020-04-10T22:20:35-0500] [ALPM] upgraded pipewire (0.2.7-2 -> 0.3.2-2)
[2020-04-10T22:20:36-0500] [ALPM] upgraded sddm (0.18.1-4 -> 0.18.1-5)
After this a reboot greeted me with a blacked out SDDM showing a mouse pointer and a frozen tty cursor.
I checked several logs of X, 66 and SDDM itself without many hints.
@ Fungal I didn't read everything here, sorry, but if you only want to change the terminal for SDDM simply edit the [X11] section in one of the SDDM config locations:
[X11]
# The lowest virtual terminal number that will be used.
MinimumVT=7
After playing around a bit, reinstalling packages, reworking services etc. etc. and switching to another theme I suddenly got a rather famous error (at least for me):
"Configuration file /var/lib/sddm/.config/sddm-greeterrc not writable.
Please contact your system administrator."
So I contacted myself and touched that file. After that SDDM would still throw the error on start up but after clicking it away it would work as expected. So I checked permissions and it was chown root:root
I figured since SDDM is complaining literally about this I'd change that files ownership to sddm:sddm and since then it works fine.
The sad thing about this story is that it seems that my Sugar Candy theme might be broken and I got no clue as to why. It worked fine before. I'll have to check this as soon as possible.
Edit:
I removed, uninstalled and reinstalled Sugar Candy from the KDE system settings module and tested a bit. As I'm testing this on my legacy-obsolete-2006-MacBook-Pro the QML blur effect caused issues on this machine. When disabling the blur effect in the themes config it works just fine. So I suppose Sugar Candy works? Please try to play around with the themes config and disable all fancy stuff if you got problems. I wouldn't want people to have issues with my theme if it was some config error from my end. Please let me know anything you find out.
