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 On 2018/06/27 17:31, trondd wrote: > On Wed, June 27, 2018 5:25 pm, Stuart Henderson wrote: > > On 2018/06/27 21:35, Klemens Nanni wrote: > >> Looks good diff-wise, although it fails to start (presumably because > >> dbus is not running); I couldn't find information in the port telling > >> me that it needs to be running. > >> > >> $ gpodder > >> 1530127951.459232 [gpodder.log] ERROR: Uncaught exception: Traceback > >> (most recent call last): > >> File "/usr/local/bin/gpodder", line 158, in <module> > >> main() > >> File "/usr/local/bin/gpodder", line 125, in main > >> session_bus = dbus.SessionBus() > >> File "/usr/local/lib/python3.6/site-packages/dbus/_dbus.py", line 211, > >> in __new__ > >> mainloop=mainloop) > >> File "/usr/local/lib/python3.6/site-packages/dbus/_dbus.py", line 100, > >> in __new__ > >> bus = BusConnection.__new__(subclass, bus_type, mainloop=mainloop) > >> File "/usr/local/lib/python3.6/site-packages/dbus/bus.py", line 122, > >> in __new__ > >> bus = cls._new_for_bus(address_or_type, mainloop=mainloop) > >> dbus.exceptions.DBusException: org.freedesktop.DBus.Error.NotSupported: > >> Using X11 for dbus-daemon autolaunch was disabled at compile time, set > >> your DBUS_SESSION_BUS_ADDRESS instead > > > > This is unlikely to be new with the update - autolaunch was disabled > > because firefox. > > > > I feel like I did see this before updating and I think fixed it previously > because firefox. > > Are we just adding a pkg-readme for all such ports? tracking down all ports that might use dbus and adding a readme (and keeping on top of this for future ports) seems pretty ridiculous.. the firefox problem is that it's autolaunching dbus from a process which has pledged that it won't start processes. so people that were relying on firefox autolaunching dbus (rather than starting it themselves e.g. from .xsession) were getting crashes. the workaround that was made was to change dbus to disable autolaunch, but (as seen here) this causes problems for other ports. landry, I know you hate wrapper scripts, but adding one for Firefox to start dbus if needed and moving the dbus port back to autolaunch would really seem a simple way to unbreak things (and I think probably a bit more widely acceptable than "change /etc/X11/xenodm/Xsession to launch dbus if present" would be ...)
