https://bugs.kde.org/show_bug.cgi?id=404335
--- Comment #12 from Fabian Vogt <fab...@ritter-vogt.de> --- (In reply to David Edmundson from comment #11) > >There's simply no alternative. That seems to be the consensus on > >https://github.com/bus1/dbus-broker/issues/145 as well. > > Ack, but I've personally changed my mind about whether it's our > responsibility to do any kind of fallback. > (https://phabricator.kde.org/D19004) > > dbus-broker and dbus-daemon are both socket activated. On all good setups it > will "just work". > > It was just a hack for an old Ubuntu at the time, but that's no longer the > case. Unless on X11, where a property is changed on the root window, DBUS_SESSION_BUS_ADDRESS has to be set in the environment to have a common session bus. So unless DBus is explicitly started by a parent process in one way or another, this is actually not enough AFAICT. With systemd, pam_systemd takes care of that I think, but what is on systems where this isn't the case, like without systemd or on FreeBSD, where DBus is an "afterthought"? The method of only using dbus-run-session if DBUS_SESSION_BUS_ADDRESS is unset seems the safest. -- You are receiving this mail because: You are watching all bug changes.
