You are not logged in.

#1 2013-02-05 20:33:14

Feynman
Member
From: Atlanta, GA, USA
Registered: 2008-05-06
Posts: 24

[SOLVED] systemd --user: "Failed to open private bus connection:"

EDIT: The solution was to set DBUS_SESSION_BUS_ADDRESS, as suggested by gtmanfred in irc.  By putting the following before executing systemd --user, the error vanished:

export DBUS_SESSION_BUS_ADDRESS=/run/user/$(id -u)/dbus/user_bus_socket

===================
Original problem:

Everything on my box appears to be working ok, but I'm getting this error consistently in tty1 and at the top of journalctl (as user) whenever I start systemd --user:

systemd[3975]: Failed to open private bus connection: Unable to autolaunch a dbus-daemon without a $DISPLAY for X11

I roughly have my system setup per this wiki section https://wiki.archlinux.org/index.php/Sy … ur_Session.  I start systemd --user via a small script in my .bash_profile. Here are my relevant dbus{.service,socket} files, from the package user-session-units mentioned in the wiki:  (Edit: xorg is started through xorg-launch-helper, also from that wiki page)  Edit2: I'm not using autologin.  I noticed that under the autologin section of that page, DBUS_SESSION_BUS_ADDRESS is set to some path.  In my setup that isn't set anywhere, so I may try to copy that later but I don't have time to play with it right now.  Will post back later.

=====/usr/lib/systemd/user/dbus.service=====

[Unit]
Description=D-Bus System Message Bus
Requires=dbus.socket

[Service]
ExecStart=/usr/bin/dbus-daemon --session --address=systemd: --nofork --systemd-activation
ExecReload=/usr/bin/dbus-send --print-reply --session --type=method_call --dest=org.freedesktop.DBus / org.freedesktop.DBus.ReloadConfig

=====/usr/lib/systemd/user/dbus.socket=====
[Unit]
Description=D-Bus System Message Bus Socket

[Socket]
ListenStream=%t/dbus/user_bus_socket

And the output of sudo systemctl status dbus:

dbus.service - D-Bus System Message Bus
	  Loaded: loaded (/usr/lib/systemd/system/dbus.service; static)
	  Active: active (running) since Tue 2013-02-05 14:50:30 EST; 22min ago
	Main PID: 369 (dbus-daemon)
	  CGroup: name=systemd:/system/dbus.service
		  └─369 /usr/bin/dbus-daemon --system --address=systemd: --no...

Feb 05 14:50:30 sellers-laptop systemd[1]: Starting D-Bus System Message Bus...
Feb 05 14:50:30 sellers-laptop systemd[1]: Started D-Bus System Message Bus.
Feb 05 14:51:18 sellers-laptop dbus-daemon[369]: dbus[369]: [system] Activating via systemd: service name='org.freedesktop.Avahi' unit='dbus-org.freedesktop.Avahi.service'
Feb 05 14:51:18 sellers-laptop dbus[369]: [system] Activating via systemd: service name='org.freedesktop.Avahi' unit='dbus-org.freedesktop.Avahi.service'
Feb 05 14:51:18 sellers-laptop dbus[369]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.Avahi.service': Unit dbus-org.freedesktop.Avahi.service failed to load: No such file or directory. See system logs and 'systemctl status dbus-org.freedesktop.Avahi.service' for details.
Feb 05 14:51:18 sellers-laptop dbus-daemon[369]: dbus[369]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.Avahi.service': Unit dbus-org.freedesktop.Avahi.service failed to load: No such file or directory. See system logs and 'systemctl status dbus-org.freedesktop.Avahi.service' for details.

.

I'm not sure what the error even means or how to go about debugging it.  Any suggestions would be appreciated.

Last edited by Feynman (2013-02-05 22:07:23)

Offline

#2 2013-02-05 22:32:24

the sad clown
Member
From: 192.168.0.X
Registered: 2011-03-20
Posts: 837

Re: [SOLVED] systemd --user: "Failed to open private bus connection:"

NVM...didn't notice it was already solved.

Last edited by the sad clown (2013-02-05 22:33:10)


I laugh, yet the joke is on me

Offline

Board footer

Powered by FluxBB