On Thu, Jun 28, 2018 at 12:01:12AM +0100, Stuart Henderson wrote: > On 2018/06/27 22:22, Landry Breuil wrote: > > The ecosystem is not really ready for not having dbus, as before the > > failure was silently hidden behind autolaunching. > > > > Generally, i'd advise anyone not running dbus on purpose for whatever > > reason to set DBUS_SESSION_BUS_ADDRESS to a bogus value, and hope that > > applications gracefully handle a broken bus. Or run a session dbus. > > it doesn't work in gpodder, I've tried a few bogus values, all fail .. > > DBUS_SESSION_BUS_ADDRESS=unix:path=/tmp/daskasdjdkjaskdjask,guid=kasdkasdkasjkdjakdjask > gpodder > DBUS_SESSION_BUS_ADDRESS=bogus gpodder > DBUS_SESSION_BUS_ADDRESS=bogus: gpodder > DBUS_SESSION_BUS_ADDRESS=tcp: gpodder > DBUS_SESSION_BUS_ADDRESS=tcp:port=12832 gpodder
Disabling dbus autolaunch was committed early on purpose so that we can see the implications. If we need to re-enable it for the time being until we have a proper solution, I am not against it. Adding pkg-readmes to all ports requiring a user dbus-session does *not* seem like the right thing to do :-) -- Antoine
