Christopher Schramm

@clefebvre: Yeah, sure. It's not included in 2.3.1 and just avoids that error "accidentally". It makes sense that it might show up in your version as well. The question remains...

@clefebvre: Yeah, just as expected. blueman-mechanism's issue is the crucial part. We do not seem to have any data on that yet.

I think we could use GTK+ power, namely `gtk_application_inhibit` with `GTK_APPLICATION_INHIBIT_IDLE` and `gtk_application_uninhibit`. To my understanding it would save us from the X11 interaction as GTK+ will route it to...

#1406 added support for `CTRL-Q` and `CTRL-W`. It's in master and will be part of 2.2.

Unfortunately not. It only applies to blueman-manager. The plugin dialog is part of blueman-applet and the adapters are blueman-adapters. It would be the same logic for blueman-adapters but blueman-applet is...

As I said, it's trivial for blueman-adapters, so I guess it's worth it. Regarding blueman-applet we'd have to switch it to GtkApplication to get the same. I'm not sure if...

Not sure about the `EAGAIN`. I have to check how https://github.com/blueman-project/blueman/issues/1363#issuecomment-733999432 behaves with 5.62+.

Meh. As expected I do get the fallback `br-connection-unknown` in the `EAGAIN` case now, so #1485 probably stopped working with BlueZ 5.62. Not sure if #1398 is still relevant with...

The description was missing. I fixed your markup and can replicate the behavior. Thanks for the report! :slightly_smiling_face:

Not really sure what you mean. I guess it's about disabled Bluetooth, i.e. existing adapters are not powered. In that case, blueman-manager shows a hint and a way to power...