Yes, both libdbus and GDBus (in gio) will spawn a new bus with dbus- launch if it can't connect to a session bus (ie, if DBUS_SESSION_BUS_ADDRESS is unset).
I've just been bitten by this in Ubuntu with IPC xpcshell tests hanging our builds. I did some investigation of this today and found that the hangs were caused by plugin-container failing to start because it couldn't get an X connection - because of the bazillion or so dbus- launch processes (and associated buses!!) that had been spawned during the previous tests had used up all of the allowable X server connections :( To work around this, we'll probably run all of the tests inside dbus- launch so that they have a bus already (eg, dbus-launch --exit-with- session) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/857153 Title: Needs to get accessibility settings from GSettings Status in The Mozilla Firefox Browser: Confirmed Status in “firefox” package in Ubuntu: Triaged Status in “firefox” source package in Oneiric: Triaged Status in “firefox” source package in Precise: Triaged Bug description: Luke mentioned to me in Dublin that the screen reader doesn't work with Firefox when accessibility is enabled. This is because Firefox is still using GConf to check if accessibility is enabled, when it really needs to be using GSettings. I've just realized this is still the case, so I assume that the screen reader still won't work by default To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/857153/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp