Comment 5 for bug 853519

Hmm, this is bothering me (failing thread):

#11 0x00007f34324c4b54 in dbus_bus_register (connection=0x7f341800acb0, error=0x7f341e8e1e10) at ../../dbus/dbus-bus.c:698
        message = 0x1b2d5d0
        reply = <optimized out>
        name = <optimized out>
        bd = 0x7f3418008640
        retval = 0
        __FUNCTION__ = "dbus_bus_register"

Another thread:

#6 0x00007f34324c4b54 in dbus_bus_register (connection=0x1b410e0, error=0x7f341f0e2dd0) at ../../dbus/dbus-bus.c:698
        message = 0x1b1d670
        reply = <optimized out>
        name = <optimized out>
        bd = 0x191e100
        retval = 0
        __FUNCTION__ = "dbus_bus_register"

Apart from the bd pointer being very different on these threads, two threads shouldn't be at ../../dbus/dbus-bus.c:698 at the same time, because that line is protected by a mutex calles "bus_data".
Reassigning to dbus for further analysis.