GNOME Bugzilla – Bug 309232
Doesn't like when bluetooth service is restarted
Last modified: 2009-06-29 09:40:43 UTC
1. Launch gnome-obex-server 2. Relaunch hcid 3. Watch it crap itself conn_request: bdaddr 00:0E:07:37:D1:B2 conn_complete: status 0x00 (Current CVS HEAD)
One of the problems is that the sdp record gets cleared. No solutions yet: http://article.gmane.org/gmane.linux.bluez.devel/7566
Still current, for both the ObexFTP and ObexPush backends. The servers get nicely killed for obex-data-server. We'd need to listen to SessionRemoved() and either try to reinit using CreateBluetoothServer() regularly (huhu), or actively listen to DBus to see if hcid is running.
This also happens when the last bluetooth device is removed/deactivated.
commit a7eff0730cab9758588f04ee728f503a8657bc69 Author: Bastien Nocera <hadess@hadess.net> Date: Mon Jun 29 10:38:36 2009 +0100 Bug 309232 – Doesn't like when bluetooth service is restarted Use BluetoothClient to monitor bluetoothd availability This means that we can bring down the obex service when there's no Bluetooth adapters available, or bluetoothd has exited.