> > You seem to be using some mechanism for starting 'systemd --user' that > gives it a DBUS_SESSION_BUS_ADDRESS that assumes dbus-daemon is being > started via a specific third-party implementation of a dbus.service for > the user bus, possibly from "user-session-units". If you use the part of > user-session-units that assumes a dbus-daemon will be launched, but not > the part that actually launches the dbus-daemon, then I'm afraid you get > to keep both pieces. > > Neither dbus nor systemd currently ships that dbus.service. When I > suggested adding one to dbus, Lennart asked me to use a different path > for the socket, then said he had no plans to support a non-kdbus user > bus at all ... so that feature request is on hold. > (https://bugs.freedesktop.org/show_bug.cgi?id=61301 if you're interested.) > > Find what is setting DBUS_SESSION_BUS_ADDRESS, and make it not do that. > > autolaunch is a mechanism to start a dbus-daemon per (machine, X11 > display) pair when no dbus-daemon is running and an application tries to > connect to D-Bus. It mostly works via X11 properties; the files in > ~/.dbus are a fallback.
After carefully reading dbus-launch(1), I understand now the fall back mechanism. Fom man : <You can always avoid autolaunch by manually setting DBUS_SESSION_BUS_ADDRESS> I have this drop-in config as recommanded by my distro (Archlinux) wiki[0]: /etc/systemd/system/user@.service.d/dbus.conf ----------------------------- [Service] Environment=DBUS_SESSION_BUS_ADDRESS=unix:path=/run/user/%I/dbus/user_bus_socket ----------------------------------- I start systemd --user as described in wiki. [0]https://wiki.archlinux.org/index.php/Systemd/User _______________________________________________ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel