ck-launch-session doesn't set x11-display-device
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
consolekit (Ubuntu) |
Won't Fix
|
Undecided
|
Unassigned | ||
ltsp (Ubuntu) |
Fix Released
|
Undecided
|
Alkis Georgopoulos |
Bug Description
Binary package hint: consolekit
consolekit version: 0.4.1-3ubuntu1 (Lucid alpha3)
In /etc/X11/
This is true for example in LTSP, which uses LDM instead of GDM.
The problem is that ck-launch-session doesn't set x11-display-device, so ck-list-sessions for that session contains:
active = FALSE
x11-display = ':0'
x11-display-device = ''
display-device = '/dev/pts/0'
If I replace that ck-launch-session call with a python script of my own, which calls OpenSessionWith
params.append (("x11-
instead, then the session correctly contains:
active = TRUE
x11-display = ':0'
x11-display-device = '/dev/tty7'
display-device = ''
Maybe the problem is that ck-launch-session doesn't have the necessary permissions to call `fgconsole` to check the active tty, and so it should find some non privileged way to do it?
Of course, the end result is that PolicyKit doesn't work as expected, since the session is considered not active, so we can't mount drives etc.
Changed in ltsp (Ubuntu): | |
assignee: | nobody → Alkis Georgopoulos (alkisg) |
This was fixed in LTSP 5.2. `su` was used instead of `ck-launch- session` , along with $CKCON_X11_DISPLAY and $CKCON_ X11_DISPLAY_ DEVICE pam environment parameters, so that now LTSP fat clients properly get an active CK session.
Closing in LTSP, the problem is still there on consolekit though.