X apps that use dbus (GTK, Firefox) either don't start or take a very long time to start

[dinamic]

ubuntu 16.10 + proposed / unity8 - desktop x86

libertine apps don't work anymore
attached are firefox and nautilus logs

[dinamic (dinamic6661)]

if i launch firefox on Xmir from the terminal, firefox starts and runs fine

[Christopher Townsend (townsend)]

Looks to be a potential regression in Xmir due to the backtrace in the Firefox log. Adding that package to the bug.

[Daniel van Vugt (vanvugt)]

It appears again that Xmir is crashing after the client has failed to start and not vice-versa.

That Xmir crash is fixed here:
https://git.launchpad.net/~xmir-team/xorg-server/+git/xmir/commit/?id=f72fad2cd4b8d6fbdef0335fbfa11e2ca38d3f86

But the Xmir crash is not causing the client start-up failure. The client start-up failure is causing the Xmir crash.

[Daniel van Vugt (vanvugt)]

Confirmed there's a regression on 16.10 where dbus functionality is missing. This causes complex apps like Firefox and Nautilus/GTK apps to hang on start-up. But it doesn't impact simpler native X apps (like bitmap or xedit).

[Daniel van Vugt (vanvugt)]

Basically any app with a menu bar will be super slow to start :(

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Daniel van Vugt (vanvugt)]

(sol:4550): GConf-WARNING **: Client failed to connect to the D-BUS daemon:
Failed to connect to socket /tmp/dbus-7HXS9fyRLw: Connection refused
GConf Error: No D-BUS daemon running

(sol:4550): GConf-WARNING **: Client failed to connect to the D-BUS daemon:
Failed to connect to socket /tmp/dbus-JQmq3lVB3z: Connection refused
GConf Error: No D-BUS daemon running

(sol:4550): GConf-WARNING **: Client failed to connect to the D-BUS daemon:
Failed to connect to socket /tmp/dbus-JQmq3lVB3z: Connection refused
GConf Error: No D-BUS daemon running

(sol:4550): GConf-WARNING **: Client failed to connect to the D-BUS daemon:
Failed to connect to socket /tmp/dbus-JQmq3lVB3z: Connection refused
GConf Error: No D-BUS daemon running

(sol:4550): GConf-WARNING **: Client failed to connect to the D-BUS daemon:
Failed to connect to socket /tmp/dbus-JQmq3lVB3z: Connection refused
GConf Error: No D-BUS daemon running

[Jamie Strandboge (jdstrand)]

Could this be related to https://bugs.launchpad.net/bugs/1604872 ?

[Christopher Townsend (townsend)]

Strange, I'm running a fully updated Yakkety system and Firefox and Gtk apps start just fine in the Yakkety based Libertine container. The Mir error in the attached logs look really fishy though...

[Daniel van Vugt (vanvugt)]

Sorry, we have a mess of duplicate bugs open...

The dbus errors: bug 1604704, bug 1604872
Xmir crashes after the first client/window exits: bug 1602561

They all overlap in slightly different ways, so deduplicating them is tricky.

[Daniel van Vugt (vanvugt)]

Please excuse the mess of duplicate bugs.

We shall track the dbus errors/hang on yakkety as bug 1604872, and the Xmir crash as bug 1602561.

Both issues have fixes ready for release already.

[Daniel van Vugt (vanvugt)]

I'm making this a duplicate of bug 1604704 now which is clearer.

The fix for bug 1604872 has not solved it.