Debugging a DBus disconnect issue.

[Rahul Chaturvedi]

I am working on the BLE advertising API and running into a roadblock. For some reason, right after my DBus call to register an advertisement, I get this error,

[23145:23154:0707/152552:FATAL:bus.cc(1193)] D-Bus connection was disconnected. Aborting.

This crashes Chrome. With all logs turned up to max, "nothing" else shows up in the Chrome logs. Watching /var/log/messages also doesn't show anything at all.

Is there some way I can turn up the logging for DBus so I can see what exactly is going wrong?

Thanks!

/rkc

[Daniel Erat]

Is the dbus-daemon process actually dying?

--
--
Chromium OS Developers mailing list: chromiu...@chromium.org
View archives, change email options, or unsubscribe:
http://groups.google.com/a/chromium.org/group/chromium-os-dev?hl=en

[Rahul Chaturvedi]

Nope. The dbus-daemon process remains up.

[Satoru Takabayashi]

That's very weird. Could you upload the code? Since this problem does not happen with other D-Bus clients, your code should be doing something different. :)

[Rahul Chaturvedi]

Uploaded here: https://codereview.chromium.org/1226443006/

A link to a test extension is in the CL comments.

On adding the --debug flag to bluetoothd shows these logs,

2015-07-07T18:37:11.673325-04:00 DEBUG bluetoothd[1331]: src/agent.c:agent_disconnect() Agent :1.9 disconnected

2015-07-07T18:37:11.673347-04:00 DEBUG bluetoothd[1331]: src/agent.c:remove_default_agent() Default agent cleared

2015-07-07T18:37:11.673352-04:00 DEBUG bluetoothd[1331]: src/agent.c:agent_destroy() agent :1.9

2015-07-07T18:37:11.673356-04:00 DEBUG bluetoothd[1331]: src/agent.c:agent_unref() 0x7f116861afc0: ref=0

Due to the log resolution for Chrome, I can't quite tell whether it is Chrome disconnecting first or bluetoothd. Speaking with jamuraa@, he believes that Chrome (or DBus) is disconnecting and bluetoothd is just doing the correct thing.

Again, I have no idea to figure out why dbus would be causing the disconnect. Using dbus-monitor --system doesn't show anything useful.

[Christopher Wiley]

You're not connected to bluetoothd, you're connected to the dbus system daemon.  That assert is saying that your connection to the system daemon has been severed.  Since the system daemon has not in fact died, it's something that Chrome is doing.

I don't know much about bluetoothd, but perhaps Chrome is registering itself with bluetoothd, and those messages are bluetoothd tearing down local state tracking Chrome?

To unsubscribe from this group and stop receiving emails from it, send an email to chromium-os-d...@chromium.org.

[Rahul Chaturvedi]

Adding Marie; I know next to nothing about bluetoothd.

[Marie Janssen]

Sorry for my late reply, but yes. these log messages are bluetoothd
tearing down it's tracking of the dbus agent which represents Chrome.
You would get it any time that Chrome is booted from the dbus.

--
Marie Janssen