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