Bug 4644 - Gnome Shell fails to start in a ThinLinc session on Ubuntu 13.04
Summary: Gnome Shell fails to start in a ThinLinc session on Ubuntu 13.04
Status: CLOSED DUPLICATE of bug 3836
Alias: None
Product: ThinLinc
Classification: Unclassified
Component: Server OS (show other bugs)
Version: 4.0.0
Hardware: PC Unknown
: P2 Normal
Target Milestone: 4.1.0
Assignee: Pierre Ossman
URL:
Keywords: aaron_tester
Depends on:
Blocks:
 
Reported: 2013-05-13 16:47 CEST by Aaron Sowry
Modified: 2013-05-15 14:21 CEST (History)
0 users

See Also:
Acceptance Criteria:


Attachments

Description Aaron Sowry cendio 2013-05-13 16:47:21 CEST
Get a number of errors similar to this in xinit.log:

Window manager warning: Log level 32: Execution of main.js threw exception: Gio.IOErrorEnum: GDBus.Error:org.freedesktop.ConsoleKit.Manager.GeneralError: Unable to lookup session information for process '13425'
Comment 1 Aaron Sowry cendio 2013-05-13 17:08:15 CEST
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
Comment 2 Aaron Sowry cendio 2013-05-14 09:29:53 CEST
(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
Comment 3 Pierre Ossman cendio 2013-05-14 14:11:01 CEST
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.
Comment 4 Pierre Ossman cendio 2013-05-14 14:32:44 CEST
Fixed in r27374.
Comment 5 Peter Åstrand cendio 2013-05-14 19:08:22 CEST

*** This bug has been marked as a duplicate of bug 3836 ***

Note You need to log in before you can comment on or make changes to this bug.