Public bug reported:
$ /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
** Affects: dbus (Ubuntu)
Importance: Undecided
Status: New
** Affects: gtk+3.0 (Ubuntu)
Importance: Undecided
Status: New
** Tags: gtk-mir regression
** Also affects: dbus (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gtk+3.0 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
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/1604704/+subscriptions
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
