[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]

Actually it's only really slow under Xmir. Native Mir gets the same
errors but no delay...

Xmir:

$ /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

Mir:

$ /usr/games/sol

(sol:20759): Gtk-WARNING **: GtkSettings Cursor Theme: Unsupported GDK
backend


(sol:20759): GConf-WARNING **: Client failed to connect to the D-BUS daemon:
Unable to autolaunch a dbus-daemon without a $DISPLAY for X11
GConf Error: No D-BUS daemon running


(sol:20759): GConf-WARNING **: Client failed to connect to the D-BUS daemon:
Unable to autolaunch a dbus-daemon without a $DISPLAY for X11
GConf Error: No D-BUS daemon running

-- 
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