desktop-packages team mailing list archive
-
desktop-packages team
-
Mailing list archive
-
Message #39706
[Bug 874924] Re: WARNING: Failed to open CK session: Timeout was reached (ecryptfs subdir)
Adding some other possibly relevant info:
- My ~/.ecryptfs does _not_ have the "auto-mount" file, i.e. it will not be mounted automatically when I log in. Could something be waiting for ~/Private to be automounted when it won't be?
I notice that the reporter of bug #872939 had a similar ecryptfs setup.
- The permissions on my ~/Private directory are as follows (output of ls -ld):
dr-x------ 2 vegar vegar 4096 2011-02-18 20:54 Private/
(note the lack of write permissions - I don't know whether this is normal or not)
This bug is probably a duplicate of bug #872939, as many of the symptoms are similar (including the workaround).
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/874924
Title:
WARNING: Failed to open CK session: Timeout was reached (ecryptfs
subdir)
Status in “lightdm” package in Ubuntu:
New
Bug description:
During the upgrade to Oneiric I chose to use lightdm instead of gdm.
After rebooting, nothing seemed to work properly. I could not
configure wifi, shut down, reboot, mount USB drives, etc. All I got
was an error message saying "Not authorized".
Running ck-list-sessions gave no output at all.
Changing back to gdm fixed the issue.
ProblemType: Bug
DistroRelease: Ubuntu 11.10
Package: lightdm 1.0.1-0ubuntu6
ProcVersionSignature: Ubuntu 3.0.0-12.20-generic-pae 3.0.4
Uname: Linux 3.0.0-12-generic-pae i686
NonfreeKernelModules: nvidia
ApportVersion: 1.23-0ubuntu3
Architecture: i386
Date: Sat Oct 15 11:56:15 2011
EcryptfsInUse: Yes
ProcEnviron:
LANGUAGE=nb_NO:nb:no_NO:no:nn_NO:nn:en_GB:en
PATH=(custom, user)
LANG=nb_NO.UTF-8
SHELL=/bin/bash
SourcePackage: lightdm
UpgradeStatus: Upgraded to oneiric on 2011-10-14 (0 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/874924/+subscriptions
Follow ups
References