I am having multiple issues with my KDE desktop since upgrading to F33.
Some background that may be significant. My system (and the existing users on it) was originally installed in September 2013 (i.e. Fedora 19 time frame). The user environments date back to then and the system has been continuously upgraded (not reinstalled) since then. Hence there are potentially lots of legacy configuration files/settings that may be causing issues.
- When logging in to existing user accounts the task bar doesn’t appear and there is no background menu available. .xsession-errors contained messages about failing to start kwin because there were other window managers running and plasma shell crashing. After a lot of trial and error I finally found that changing:
in ~/.config/plasma-org.kde.plasma.desktop-appletsrc fixed the issue. Hence this problem is solved for me but why did this happen and is the issue documented anywhere? This may be related to the fact that I used the “legacy” menu (or whatever it was called) in the application launcher.
- The screen locker is broken (and is not fixed by the update to xscreensaver 5.44-9 that has just come out). If I attempt to lock the screen I get the message:
The screen locker is broken and unlocking is not possible anymore.
In order to unlock switch to a virtual terminal (e.g. Ctrl+Alt+F2),
login and execute the command:
loginctl unlock-session <N>
Afterwards switch back to the running session (Ctrl+Alt+F1)
This affects all users - both existing users and newly created accounts.
- Leaving/shutting down session
Again this affects all users both existing and newly created.
a) If I select the leave tab in the application launcher (or even simply hover over it) plasma shell crashes and restarts and nothing else (!) happens
b) If I use the RMB on the desktop (or Ctrl+Alt+Del) the user gets logged out immediately - no options, no timeout. The same is true if I select the power off button from the Lock/Logout widget on the task bar
c) If I attempt to switch users using the Lock/Logout widget it fails because it can’t screen lock the existing user - see (2) above