[Bug 1604704] Re: [regression] GTK apps hang for a very long time on start-up under Xmir and Mir failing to find dbus
Daniel van Vugt
daniel.van.vugt at canonical.com
Wed Jul 20 07:49:21 UTC 2016
It used to work immediately in xenial. Now in yakkety I get errors every
time.
Only dbus-related apps are affected. Native X11/Mir apps start
instantly.
--
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to dbus in Ubuntu.
https://bugs.launchpad.net/bugs/1604704
Title:
[regression] GTK apps hang for a very long time on start-up under Xmir
and Mir failing to find dbus
Status in dbus package in Ubuntu:
New
Status in gtk+3.0 package in Ubuntu:
New
Bug description:
$ /usr/games/sol
(sol:18808): GConf-WARNING **: Client failed to connect to the D-BUS daemon:
Failed to connect to socket /tmp/dbus-7diijTV1R5: Connection refused
GConf Error: No D-BUS daemon running
(sol:18808): GConf-WARNING **: Client failed to connect to the D-BUS daemon:
Failed to connect to socket /tmp/dbus-Zlu4hiB92O: Connection refused
GConf Error: No D-BUS daemon running
$ nautilus
(nautilus:18870): libunity-CRITICAL **: unity-launcher.vala:154:
Unable to connect to session bus: Could not connect: Connection
refused
(nautilus:18870): libunity-CRITICAL **: unity-launcher.vala:154:
Unable to connect to session bus: Could not connect: Connection
refused
(nautilus:18870): libunity-CRITICAL **: unity-launcher.vala:154:
Unable to connect to session bus: Could not connect: Connection
refused
(nautilus:18870): LIBDBUSMENU-GLIB-WARNING **: Unable to get session
bus: Could not connect: Connection refused
(nautilus:18870): LIBDBUSMENU-GLIB-WARNING **: Unable to get session
bus: Could not connect: Connection refused
(nautilus:18870): LIBDBUSMENU-GLIB-WARNING **: Unable to get session
bus: Could not connect: Connection refused
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/1604704/+subscriptions
More information about the foundations-bugs
mailing list