You are not logged in.

#1 2013-10-22 22:13:54

orschiro
Member
Registered: 2009-06-04
Posts: 2,136
Website

[solved] systemd: Failed to open private bus connection:

I get the following error message during the boot process:

Oct 23 00:07:33 thinkpad systemd[796]: Failed to open private bus connection: Failed to connect to socket /run/user/1000/dbus/user_bus_socket: No such file or directory

I couldn't find any information. What does it exactly mean?

Last edited by orschiro (2013-10-23 06:06:16)

Offline

#2 2013-10-22 22:22:15

falconindy
Developer
From: New York, USA
Registered: 2009-10-22
Posts: 4,111
Website

Re: [solved] systemd: Failed to open private bus connection:

Ignore it. It's user@1000.service starting up and not finding the dbus socket.

Offline

#3 2013-10-23 06:06:04

orschiro
Member
Registered: 2009-06-04
Posts: 2,136
Website

Re: [solved] systemd: Failed to open private bus connection:

Thanks. It is not possible to disable it when not even using private user systemd?

Offline

#4 2013-10-28 03:28:32

donniezazen
Member
From: Salt Lake City
Registered: 2011-06-24
Posts: 671
Website

Re: [solved] systemd: Failed to open private bus connection:

My KDE session isn't being started (no autostart, logout, reboot, etc.) and this is the only error shown by journalctl -b. Could these be connected?

Offline

#5 2013-10-28 07:02:21

orschiro
Member
Registered: 2009-06-04
Posts: 2,136
Website

Re: [solved] systemd: Failed to open private bus connection:

I also have another question. I read somewhere that User Systemd is nothing officially supported by systemd, though it can be used in that way. However, why does the user@1000.service start up by default then?

Offline

Board footer

Powered by FluxBB