Bugzilla – Bug 4644
Gnome Shell fails to start in a ThinLinc session on Ubuntu 13.04
Last modified: 2013-05-15 14:21:40
You need to
before you can comment on or make changes to this bug.
Get a number of errors similar to this in xinit.log:
Window manager warning: Log level 32: Execution of main.js threw exception:
Unable to lookup session information for process '13425'
I can get a functional Gnome Shell session however, by starting a terminal
session and running the following:
ck-launch-session dbus-launch gnome-session --session=gnome
(In reply to comment #1)
> I can get a functional Gnome Shell session however, by starting a terminal
> session and running the following:
> ck-launch-session dbus-launch gnome-session --session=gnome
We already start dbus as part of xstartup.d, so the following will suffice:
ck-launch-session gnome-session --session=gnome
See also bug #3796
Found a different approach to this. Ubuntu uses pam_ck_connector, but it isn't
working for us. The reason is that it gets uppity when PAM_TTY isn't set. So if
we fix that, we should get a proper ConsoleKit session.
We also want to set RHOST to make ConsoleKit register the session as remote.
Fixed in r27374.
*** This bug has been marked as a duplicate of bug 3836 ***