- Edited
Plasma 5.17 was released yesterday. I got to update today and apparently it broke right away. Is it just me?
X works fine. I'm writing from JWM. Fun fact: From within JWM I can launch any KDE app from a terminal. kate, kwrite, gwenview, kcalc, ksystemlog, dolphin and whatever else...even systemsettings5...
It looks like it's dbus again...but I'm not sure. I can not even startx it anymore. That is to say I could always run "/usr/bin/ck-launch-session dbus-launch --sh-syntax --exit-with-session startkde" manually and it would work. No services needed for that.
I also note that SDDM throws an error about "(EE) Failed to open authorization file "/var/run/sddm/{longIDnumber}": No such file or directory". I think I have had this before, but I don't remember what I did back then. There's several reports to this type of error but they all are remedied by updates or reinstalls...wtf. Still this should not prevent startx from working.
After further investigation:
There might be more to this than just dbus...
System boots -> SDDM pops up successfully -> Plasma session is selected -> KDE splash shows and loads -> KDE splash freezes and a cursors pops up which can be moved around on top of the frozen splash screen.
/var/log/Xorg.0.log does not provide any useful information
X works fine. I'm writing from JWM. Fun fact: From within JWM I can launch any KDE app from a terminal. kate, kwrite, gwenview, kcalc, ksystemlog, dolphin and whatever else...even systemsettings5...
It looks like it's dbus again...but I'm not sure. I can not even startx it anymore. That is to say I could always run "/usr/bin/ck-launch-session dbus-launch --sh-syntax --exit-with-session startkde" manually and it would work. No services needed for that.
I also note that SDDM throws an error about "(EE) Failed to open authorization file "/var/run/sddm/{longIDnumber}": No such file or directory". I think I have had this before, but I don't remember what I did back then. There's several reports to this type of error but they all are remedied by updates or reinstalls...wtf. Still this should not prevent startx from working.
After further investigation:
There might be more to this than just dbus...
To further describe the behavior:Plasma Release Announcements wrote First of all, Plasma now starts even faster! Among many other optimizations, start-up scripts have been converted from Bash (a slow, interpreted language) to C++ (a fast, compiled language) and now run asynchronously. This means they can run several tasks simultaneously, instead of having to run them one after another. As a result, the time it takes to get from the login screen to the fully loaded desktop has been reduced significantly.
System boots -> SDDM pops up successfully -> Plasma session is selected -> KDE splash shows and loads -> KDE splash freezes and a cursors pops up which can be moved around on top of the frozen splash screen.
/var/log/Xorg.0.log does not provide any useful information