Activated service 'org.freedesktop.systemd1' failed

Simon McVittie smcv at
Mon Sep 10 19:02:23 UTC 2018

On Mon, 10 Sep 2018 at 18:20:25 +0000, Дилян Палаузов wrote:
> when I enter 'XDG_SESSION_TYPE=wayland dbus-run-session gnome-session' I see
> the messages below.  My feeling is than nobody ever tried to start service
> org.freedesktop.systemd1 but a missing service … is missing.  How can I find
> out the cause for the error messages below?  I use dbus 1.12.8.

It looks as though you aren't using 'systemd --user' for this session.

If you are using systemd, then you should prefer to run GUI sessions in
a properly set up systemd-logind session (on Debian, libpam-systemd is
responsible for this; other distros will vary, but the important thing
is to be in a PAM login session and have the pam_systemd module in its
PAM stack), and preferably use dbus-daemon as a systemd user service
(for example the --enable-user-session option when configuring dbus at
build time, or the dbus-user-session package in Debian).

If you are not using systemd, don't install
/usr/share/dbus-1/*services/org.freedesktop.systemd1.service, and
dbus-daemon won't believe systemd is potentially available.

If you are using systemd, and you are deliberately using a separate
dbus-daemon per login session (not using user session mode), and you
do not require compatibility with dbus 1.10.x or older, then you can
remove /usr/share/dbus-1/*services/org.freedesktop.systemd1.service.

The /usr/share/dbus-1/*services/org.freedesktop.systemd1.service files
are dummy files with Exec=/bin/false, because systemd needed them in
order to be compatible with older dbus versions, but they are unnecessary
after has been fixed,
which was done in dbus 1.11.0. Starting systemd as a child process of
dbus-daemon can't actually work (to be the system or user service manager,
it needs to be dbus-daemon's parent, not its child) which is why there is
a dummy value in the Exec line.


More information about the dbus mailing list