kstartupconfig4 error when an user with encrypted home folder use auto-login in Kubuntu 11.04
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
kdebase (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
I have a netbook ASUS eeepc 1000HE and I installed the last Kubuntu 11.04 (32 bits) with the option to encrypt the the home folder of the user account.
I wanted to enable the Auto-Login with the only user account that I have but always after the re-boot I get a small X window error with the message: "kstartupconfig4 not exist or fails. The error code is 3".
I can click the ok button to continue the system load but I have to write the password again in the Login manager (as if the Auto-Login option was not marked) .
If I unmark again the "Enable Auto-Login" option in the "System Settings" -> "Login Screen" -> "Convenience" tab that error dissapear.
Because the auto-Login feature is very common & the only strange thing that I made is to choose the encryption of the home folder during the installation of Kubuntu 11.04 (is the first time that I choose encryption) I belive that the error is related to the combination of encryption+
affects: | ubuntu → kdebase (Ubuntu) |
tags: |
added: natty removed: kstartupconfig4 |
I guess the problem is that Auto-Login can't work together with an encrypted home directory. default/ share/config/ startupconfigke ys or ~/.kde_ default/ share/config/ startupconfigfi les and fails.
You need to provide a password in order to unencrypt your home directory. If you do not provide a password than your home directory isn't accessible and kstartupconfig4 can't read e.g. ~/.kde_
I have a similar issue without auto login.
I regularly log in with password to kde. While logging in my Private ecryptfs directory is mounted. My .kde directory resides in ~/Private/.kde. The first login after startup always works and kde starts up fine. mount-private'
When I logout of kde and try to relogin then I get the same error as javielillo. "kstartupconfig4 does not exist or fails. The error code is 3". The reason for this is that the Private directory isn't mounted after relogin. When I try to login from the console I get the error:
keyctl_search: required key not available
Perhaps try the interactive 'ecryptfs-
This seems to be an issue with ecryptfs.