bluetooth start not handled in kete

[whot]

Sequence to reproduce:

• turn bluetooth off
• start tuhi
• start kete
• turn bluetooth on

The tuhi dbus object shows the device but kete doesn't know about it. Somewhere a signal is getting lost

[bentiss]

I wonder if we really want to fix this. kete is not intended to be the final application, so if you run this, there is a high chance you know how to enable bluetooth before running kete.

I suspect we will need a bunch of bluez callbacks too, so I am reluctant to handle this case.

[whot]

kete doesn't need to, but fixing this would verify if the bug is in tuhi somewhere. Because kete shouldn't need any bluez hooks anyway, but if a tuhi dbus device doesn't show up despite it being on the bus then we have a problem.

[bentiss]

Trying to replicate here.

If I just run systemctl stop bluetooth then start tuhi, then tuhi-kete, it all seem to work well besides the fact that tuhi doesn't seem to see the discovery announcements from the device until it gets restarted.

If I click on the Bluetooth Off icon first in gnome-shell, I have a GLib.Error: g-io-error-quark: GDBus.Error:org.bluez.Error.NotReady: Resource Not Ready (36). It is kind of expected, and I think we should just relay it to the caller, no?

[bentiss]

Note that turning bluetooth On and Off influence on the property org.bluez.Adapter1.Powered. So we should be able to detect this before attempting to communicate.

[whot]

doesn't seem to see the discovery announcements from the device until it gets restarted.

iirc that's the issue, we shouldn't need to restart tuhi when bluetooth gets disabled and re-enabled.

[bentiss]

Making progresses here. I have a different behavior on my desktop than on my laptop:

• on the desktop, toggling bluetooth on/off affects the Powered property, cleans up the GATT services, but the bluez devices are kept
• on the laptop, toggling bluetooth off also removes the bluez devices.

Which means that on the laptop, if I start tuhi while bluetooth is off, it only sees the devices later, when it is turned on. However, currently there is no events emitted when Devices gets modified with already registered devices. I guess this is the issue you were seeing. You have to restart kete to get the list of devices.