On 17/11/13 16:18, Les Schaffer wrote: > On 11/16/2013 01:40 PM, Emilio Pozuelo Monfort wrote: >> Reading the relevant libpam-systemd code, it seems like libpam-systemd is >> talking to logind through dbus but logind is not running so dbus return that >> error. However if logind is not running, gnome-shell should have noticed it >> and >> decided to use the ConsoleKit support. > > quick question: i am still using sysvinit, is that ok??? will await > response to this before doing strace you requested.
Yes, that's fine. >> Is logind running? Have you done anything to enable/disable it? > > not that i know of... > >> What's the output of `ls -l /run/systemd/' ? > > speggy:~/install# ls -lR > /run/systemd/ > > > /run/systemd/: > > > total > 0 > > > drwxr-xr-x 2 root root 40 Nov 17 09:58 > inhibit > > > drwxr-xr-x 2 root root 60 Nov 17 09:41 > seats > > > drwxr-xr-x 2 root root 40 Nov 17 09:41 > sessions > > > drwxr-xr-x 2 root root 40 Nov 17 09:41 > users > > > > > > /run/systemd/inhibit: > > > total > 0 > > > > > > /run/systemd/seats: > > > total > 4 > > > -rw-r--r-- 1 root root 99 Nov 17 09:41 > seat0 > > > > > > /run/systemd/sessions: > > > total > 0 > > > > > > /run/systemd/users: > > > total 0 > > > also, is this the logind you are referring to?: > > speggy:~# ps uxwa|grep login > root 4715 0.0 0.0 28504 1552 ? S 09:41 0:00 > /lib/systemd/systemd-logind Yes, that's logind running. The problem is that when libpam-systemd tries to create a session, logind returns an error. The strace logs for the systemd-logind process may help in determining why logind can't create the session. Cheers, Emilio -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
