❦ 14 juillet 2012 13:02 CEST, Leiking <[email protected]> :
> In grub menu, I chose 5.
>
> Then ---> inittab 5 (loggin as jinleileiking)---> .zprofile ---> startx
>
>
> But, in awesome:
>
> ➜ ~ git:(master) ✗ ck-list-sessions
> Session1:
> unix-user = '1000'
> realname = '(null)'
> seat = 'Seat1'
> session-type = ''
> active = FALSE
> x11-display = ''
> x11-display-device = ''
> display-device = '/dev/tty1'
> remote-host-name = ''
> is-local = TRUE
> on-since = '2012-07-14T09:19:58.527229Z'
> login-session-id = ''
> Session2:
> unix-user = '1000'
> realname = '(null)'
> seat = 'Seat2'
> session-type = ''
> active = FALSE
> x11-display = ':0'
> x11-display-device = '/dev/tty7'
> display-device = '/dev/tty1'
> remote-host-name = ''
> is-local = FALSE
> on-since = '2012-07-14T09:20:09.346425Z'
> login-session-id = ''
>
> Session2 is not active
There was a change in console kit that did not allow a non-root user to
be considered as active. This is the job of the DM to do this
operation. Not all DM are able to do so.
You can either use GDM3 (a very lightweight DM which pulls a window
manager as a dependency) with autologin or slim (from 1.3.3 for
consolekit support), with autologin as well.
Another solution would be to investigate if you have the
pam_ck_connector.so module which may do the same things for console
users. I have it in /etc/pam.d/common-session:
session optional pam_ck_connector.so nox11
I don't know if it is enabled with your way of autologin (there is no
authentication but maybe getty is calling PAM session nonetheless).
--
Write and test a big program in small pieces.
- The Elements of Programming Style (Kernighan & Plauger)
--
To unsubscribe, send mail to [email protected].
