WARNING: Failed to open CK session: Timeout was reached (ecryptfs subdir)

[VS]

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)

[Sebastien Bacher (seb128)]

Thank you for your bug report, could you add your lightdm.log to the bug?

[Sebastien Bacher (seb128)]

the log has a that error

"[+41.99s] WARNING: Failed to open CK session: Timeout was reached"

does using ck-launch-sessions works normally?

[VS (storvann)]

What's an appropriate way to test that?

I am currently logged in using gdm, and running ck-launch-session in a terminal gives me a new shell inside the terminal (I have to run exit twice to close the terminal, as indicated below).

vegar@vegar-laptop:~$ ck-launch-session
vegar@vegar-laptop:~$ exit
exit
vegar@vegar-laptop:~$

When you mention it, I do remember a strange 'waiting period' before the desktop started loading after entering the password. That is probably lightdm waiting for CK.

If desirable, I can try to run ck-launch-session after logging in with lightdm and see if it works there.

The console-kit daemon is, btw, running like this (when using gdm):
vegar@vegar-laptop:~$ ps aux|grep console
root 1346 0.0 0.0 28248 3400 ? Sl Oct15 0:04 /usr/sbin/console-kit-daemon --no-daemon

[Sebastien Bacher (seb128)]

is there any consolekit error in your gdm logs or session logs?

the code does

" result = g_dbus_proxy_call_sync (ck_proxy,
                                     "OpenSessionWithParameters",
                                     g_variant_new ("(a(sv))", parameters),
                                     G_DBUS_CALL_FLAGS_NONE,
                                     -1,
                                     NULL,
                                     &error);

    if (error)
        g_warning ("Failed to open CK session: %s", error->message);"

so it seems that for your the "OpenSessionWithParameters" ck call is taking longer than the timeout...

[VS (storvann)]

Consolekit/policykit was only mentioned once in /var/log/gdm/:0-slave.log and once in ~/.xsession-errors, but no error (both files attached).

I should probably also mention that I am using Xubuntu (I installed the xubuntu-desktop package about a month before the upgrade to oneiric).

[Sebastien Bacher (seb128)]

seems a bit similar to bug #872939, is your configuration similar to the one on this bug?

[VS (storvann)]

I do not experience all the issues mentioned in #872939 (for example, gdm wasn't affected in my case), and I have a 32-bit system, and I don't use unity, but I can confirm that renaming ~/.ecryptfs fixes all my issues when using lightdm.

Relevant info: I have an encrypted ~/Private

[VS (storvann)]

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).

[Dustin Kirkland  (kirkland)]

Do you have any configuration information, directories or files that
lightdm might need stashed in your non-auto-mounted Private dir?

[VS (storvann)]

Nope. It only contains some pdf and png files.

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[stop (whoopwhoop)]

I have same problems, using a non-auto-mount ~/Private folder containing non-essential files on a 64 bit machine. CPU is 100% all of the time, all kinds of stuff like audio and network are not working properly...

[Miłosz Kosobucki (mikom)]

This bug is quite severe. It left me with almost unusable system. Even after reinstallation it wasn't working properly because there was still this .ecryptfs folder (I preserved my /home volume).

Is there any workaround beyond making your Private folder unusable?

[VS (storvann)]

Yes. Use gdm instead of lightdm: apt-get install gdm

[Miłosz Kosobucki (mikom)]

Does _anyone_ take this seriously?

[Sebastien Bacher (seb128)]

The bug is triaged as High and will be looked at this cycle, people are just busy and the end of year is usually low activity time, not sure where the issue is, lightdm got it but it seems consolekit timeouts due to those non automounted ecryptfs private dirs, not sure why those create issues for ck though. I'm adding consolekit and ecryptfs-utils components for now since it might be an issue there

[Evan Peck (colors)]

Is the error in ecryptfs-utils?

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Tyler Hicks (tyhicks)]

Marking the ecryptfs-utils task as invalid. Encryption is a cpu intensive operation and there's nothing that can be done, from an eCryptfs standpoint, for this specific bug.

Software depending on hard-coded timeout values is troublesome since the home directory may be encrypted, may be in an NFS mount over a slow network connection, etc.

[Robert Ancell (robert-ancell)]

Closing this bug since it is so old. Please open new bugs if you are still getting issues like this.