You are not logged in.
I'm probably to dumb to figure out how to avoid the inactive session problem on fluxbox (see below)
Using qingy (1.0) this is how I start fluxbox
exec ck-launch-session dbus-launch --sh-syntax --exit-with-session startfluxbox
In my understanding ths all it takes for an active session
yet ck-list-sessions still gives
Session1:
unix-user = '1000'
realname = '(null)'
seat = 'Seat2'
session-type = ''
active = FALSE
x11-display = ':1'
x11-display-device = '/dev/tty3'
display-device = '/dev/tty1'
remote-host-name = ''
is-local = FALSE
on-since = '2012-04-09T16:49:18.486520Z'
login-session-id = ''
For completeness' sake here is also
/etc/pam.d/qingy
auth required pam_tally2.so onerr=succeed
auth required pam_shells.so
auth required pam_nologin.so
auth include system-auth
account required pam_access.so
account required pam_nologin.so
account include system-auth
account required pam_tally2.so onerr=succeed
password include system-auth
session optional pam_loginuid.so # comes before the pam_ck_connector
session required pam_env.so
session optional pam_lastlog.so
session include system-auth
session optional pam_ck_connector.so
session optional pam_motd.so motd=/etc/motd
session optional pam_mail.so
I should add that both consolekit and plokit are installed and running
Last edited by goodboy (2012-04-09 17:44:01)
Offline
Well just in the likelyhood someone else stumbles over this thread. After much searching and reading I conclude Qingy as for now isnt woth trying. Not as long as you need proper console-kit support. Some applications for instance need a working keyring manager which itself relies on an active console-kit session. Other than that I really liked qingy. I'm now back to the good old startx resulting in an active session and a working gnome keyring.
Last edited by goodboy (2012-04-09 22:09:41)
Offline
After much searching and reading I conclude Qingy as for now isnt woth trying. Not as long as you need proper console-kit support.
I use qingy with console-kit and openbox without any problems. Have you worked around the locked tty issue by putting
openvt -c 63 -f -- console-kit-daemon --no-daemon &in rc.local? It's at the bottom of the wiki page for qingy.
Offline
goodboy wrote:After much searching and reading I conclude Qingy as for now isnt woth trying. Not as long as you need proper console-kit support.
I use qingy with console-kit and openbox without any problems. Have you worked around the locked tty issue by putting
openvt -c 63 -f -- console-kit-daemon --no-daemon &in rc.local? It's at the bottom of the wiki page for qingy.
Yes I tried that too.
Lately after working smoothly for like 5 yrs. there was yet another annoyance. If there is no activity qingy's login screen will simple black out. It resumes after you start typing (or move the mouse pointer) but disappears immediately as soon you stop. The menu had its own issues too. Well, anyway fluxbox, mingetty + autologin work perfectly now. I ditched qingy for good.
Offline