encrypted home, kdm forgets my previous session type

[Per Ångström]

KDM does not remember my last session type (Gnome or KDE), so it always logs me in to Gnome, unless I explicitly choose some other session type. When I open the session menu, I find that "restricted guest" is always marked "previous", no matter which session type I last logged in to.

ProblemType: Bug
Architecture: amd64
Date: Tue Jan 26 18:16:44 2010
DistroRelease: Ubuntu 10.04
EcryptfsInUse: Yes
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027)
NonfreeKernelModules: nvidia
Package: kdebase (not installed)
ProcVersionSignature: Ubuntu 2.6.32-11.15-generic
SourcePackage: meta-kde
Uname: Linux 2.6.32-11-generic x86_64

[Per Ångström (autark)]

I looked in my .dmrc file, and it said something like:
[Desktop]
Language=en_US.utf8
Layout=se
Session=default

I changed to "Session=kde4", which gave me a warning about a bad session type. Then I changed to "Session=kde4" and then KDM started remembering again,

I can't see what was wrong really, but now it works for me. I don't know whether I should close this bug though, because there was a problem that just came out of nowhere, so something somewhere must be wrong.

[Per Ångström (autark)]

That should be: Then I changed to "Session=kde" and then KDM started remembering again.

[Per Ångström (autark)]

After a restart, the problem has come back. But now I think I know what's causing it: I have an encrypted home partition, and KDM tries to read my preferences before I have logged in. It fails, and uses some faulty logic to determine that my previous session type was "restricted guest". It doesn't make a new try to read my preferences after I have logged in.

[Per Ångström (autark)]

I have filed an upstream bug: https://bugs.kde.org/show_bug.cgi?id=225294.

[Per Ångström (autark)]

I have updated the upstream bug with one important piece of information: The bug occurs only if one has disabled showing the user list. It seems that KDM does have provisions for handling delayed home directories, but apparently they do not cover this specific case.

[Harald Sitter (apachelogger)]

Closing in favor of report at bugs.kde.org, please refer there for status updates on this bug.
Thanks.