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 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/874924 Title: WARNING: Failed to open CK session: Timeout was reached To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/874924/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
