Hi all Got a very strange problem after one of the last updates (world emerge): After booting, at the sddm login screen, the user enters his password. The login screen then just hangs (input fields and submit buttons deactivated) forever. Switching to a text console (ctrl-alt F1) and back to F7 solves that block, and the user is presented with his desktop. But the desktop is not configured with the user settings - some items are different. And not all of the programs/widgets that were running before reboot are restored from the session. What is restored: - screen resolution - desktop background image - statically configured panel items - font size wi What is not restored: - Cursor theme - Global application font sizes (qt/gtk) - Desktop scaling (this is a HiDPI screen) - Size of panel - Running items from last session (eg. amarok, pidgin, owncloud) - None of the configured "Autostart" scripts are executed - No network connection is automatically established (although configured) If the screensaver is activated in this situation, it immediately displays an error stating (from memory) "The screensaver is broken and it is not possible to unlock the session. To unlock the session, switch to another terminal and run loginctl unlock-session". (Which is a joke in itself, as this system has no systemd ...) What's even stranger: The user then logs out of plasma, the sddm screen appears again, the user logs back in, and now all his items are restored. The running programs/widget from the last session before the reboot are also restarted. Only the network connection is still not restarted (yes, it's set to connect automatically). The behaviour is the same for all users, including freshly added test users. Don't know if this has any impact: The system's /home partition is encrypted and mounted via dmcrypt during startup.
Could you please add emerge --info, and indicate which version of Plasma is in use?
Created attachment 440574 [details] emerge --info Not sure what exactly is the plasma version. Here's some output: * kde-apps/plasma-runtime Latest version available: 16.04.2 Latest version installed: 16.04.2 * kde-frameworks/plasma Latest version available: 5.24.0 Latest version installed: 5.24.0 * kde-plasma/plasma-desktop Latest version available: 5.7.0 Latest version installed: 5.7.0 * kde-plasma/plasma-integration Latest version available: 5.7.0 Latest version installed: 5.7.0 * kde-plasma/plasma-meta Latest version available: 5.7.0 Latest version installed: 5.7.0 * kde-plasma/plasma-workspace Latest version available: 5.7.0 Latest version installed: 5.7.0
I found the reason for this strange behaviour: The /home partition was not mounted at boot due to (an error in?) dmcrypt (see https://bugs.gentoo.org/show_bug.cgi?id=591950). So after boot, an old configuration from the pre-existing user home under /home/$user was used, which should have been hidden by the crypted disk being mounted at /home.