<div dir="auto"><div><br><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Wed, Mar 6, 2019, 21:03 Julien Leproust <<a href="mailto:julien@kwet.org">julien@kwet.org</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Yes, I do have dbus-user-session and dbus-x11 installed:<br>
<br>
$ apt-cache policy dbus-user-session dbus-x11<br>
dbus-user-session:<br>
Installed: 1.12.12-1<br>
Candidate: 1.12.12-1<br>
Version table:<br>
1.13.8-1 1<br>
1 <a href="http://ftp.fr.debian.org/debian" rel="noreferrer noreferrer" target="_blank">http://ftp.fr.debian.org/debian</a> experimental/main amd64 <br>
Packages<br>
*** 1.12.12-1 500<br>
500 <a href="http://ftp.fr.debian.org/debian" rel="noreferrer noreferrer" target="_blank">http://ftp.fr.debian.org/debian</a> sid/main amd64 Packages<br>
100 /var/lib/dpkg/status<br>
dbus-x11:<br>
Installed: 1.12.12-1<br>
Candidate: 1.12.12-1<br>
Version table:<br>
1.13.8-1 1<br>
1 <a href="http://ftp.fr.debian.org/debian" rel="noreferrer noreferrer" target="_blank">http://ftp.fr.debian.org/debian</a> experimental/main amd64 <br>
Packages<br>
*** 1.12.12-1 500<br>
500 <a href="http://ftp.fr.debian.org/debian" rel="noreferrer noreferrer" target="_blank">http://ftp.fr.debian.org/debian</a> sid/main amd64 Packages<br>
100 /var/lib/dpkg/status<br>
<br>
<br>
On the other affected machine, dbus-user-session is installed but <br>
dbus-x11 isn't.<br>
<br>
I have experimental repositories configured but I don't use them currently.<br>
<br>
<br>
On Wed, 6 Mar 2019 19:35:42 -0300 Felipe Sateler <<a href="mailto:fsateler@debian.org" target="_blank" rel="noreferrer">fsateler@debian.org</a>> <br>
wrote:> So, #923881 gives one reason why systemd --user might fail. Is your<br>
> home directory set to a non-absolute path?<br>
<br>
No, my home is the standard /home/julien.<br>
<br>
> What could be helpful, is to provide the full journal from around the<br>
> time you login. There should be something there signalling why your<br>
> user instance is not starting.<br>
> <br>
> ANother thing, easier to test, is to try to launch the user manager:<br>
> `systemctl start user@$UID` . Does that work?<br>
<br>
Indeed, this works. I hadn't thought to try this.<br>
<br>
-- Logs begin at Fri 2019-03-01 10:13:47 CET, end at Thu 2019-03-07 <br>
00:44:16 CET. --<br>
Mar 07 00:40:20 treize systemd[1]: Starting User Manager for UID 1000...<br>
Mar 07 00:40:20 treize systemd[30137]: pam_unix(systemd-user:session): <br>
session opened for user julien by (uid=0)<br>
Mar 07 00:40:20 treize systemd[30137]: Listening on GnuPG cryptographic <br>
agent and passphrase cache.<br>
Mar 07 00:40:20 treize systemd[30137]: Reached target Paths.<br>
Mar 07 00:40:20 treize systemd[30137]: Listening on GnuPG cryptographic <br>
agent and passphrase cache (access for web browsers).<br>
Mar 07 00:40:20 treize systemd[30137]: Listening on Sound System.<br>
Mar 07 00:40:20 treize systemd[30137]: Listening on GnuPG network <br>
certificate management daemon.<br>
Mar 07 00:40:20 treize systemd[30137]: Starting D-Bus User Message Bus <br>
Socket.<br>
Mar 07 00:40:20 treize systemd[30137]: Reached target Timers.<br>
Mar 07 00:40:20 treize systemd[30137]: Listening on GnuPG cryptographic <br>
agent (ssh-agent emulation).<br>
Mar 07 00:40:20 treize systemd[30137]: Listening on GnuPG cryptographic <br>
agent and passphrase cache (restricted).<br>
Mar 07 00:40:20 treize systemd[30137]: Listening on D-Bus User Message <br>
Bus Socket.<br>
Mar 07 00:40:20 treize systemd[30137]: Reached target Sockets.<br>
Mar 07 00:40:20 treize systemd[30137]: Reached target Basic System.<br>
Mar 07 00:40:20 treize systemd[30137]: Reached target Default.<br>
Mar 07 00:40:20 treize systemd[30137]: Startup finished in 65ms.<br>
Mar 07 00:40:20 treize systemd[1]: Started User Manager for UID 1000.<br>
<br>
This creates /run/user/1000:<br>
$ ls -al /run/user/1000<br>
total 0<br>
drwx------ 5 julien julien 120 Mar 7 00:40 ./<br>
drwxr-xr-x 4 root root 80 Mar 7 00:40 ../<br>
srw-rw-rw- 1 julien julien 0 Mar 7 00:40 bus=<br>
drwx------ 2 julien julien 140 Mar 7 00:40 gnupg/<br>
drwxr-xr-x 2 julien julien 60 Mar 7 00:40 pulse/<br>
drwxr-xr-x 2 julien julien 80 Mar 7 00:40 systemd/<br>
<br>
Here is the lightdm journal on one of the machines where it is <br>
configured with autologin and kodi-standalone session:<br>
-- Subject: A start job for unit lightdm.service has begun execution<br>
-- A start job for unit lightdm.service has begun execution.<br>
-- Subject: A start job for unit lightdm.service has finished successfully<br>
-- A start job for unit lightdm.service has finished successfully.<br>
Mar 07 00:50:32 totoro lightdm[1008]: <br>
pam_unix(lightdm-autologin:session): session opened for user julien by <br>
(uid=0)<br>
Mar 07 00:50:32 totoro lightdm[1008]: Failed to open CK session: <br>
GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name <br>
org.freedesktop.ConsoleKit was not provided by any .service files<br></blockquote></div></div><div dir="auto"><br></div><div dir="auto"><br></div><div dir="auto">It seems yo still have pam ck connector installed. Can you confirm?</div><div dir="auto"><br></div><div dir="auto">Saludos</div><div dir="auto"><div class="gmail_quote"></div></div></div>