Sander Sweers

~~interesting. Looks like it sometimes starts, ignores the timer and exists immediately~~ I misread :eyes: I don't see it dying, it ends normally after ~30 seconds and nothing stand out...

Most devices don't show up unless you put it in a pairing state. If it still does not show follow the troubleshooting page https://github.com/blueman-project/blueman/wiki/Troubleshooting

From the message it most likely means you haven't installed the dbus service file correctly. Are you building blueman yourself?

The only reason I can think of blueman would run any networking methods on mechanism is when nap is enabled. It would be very helpful if we can get some...

I opened #1795 to at least avoid people seeing this when NAP is not enabled. I do still want to see what happens with blueman-mechanism so please do share logs.

The ImportError is raised intentionally as the plugin only works with X11 (root window). We only have one plugin that doesn't work with Wayland so adding logic for this does...

> 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...

@parr0tr1ver it is a timing issue. Delaying ``if not applet.GetBluetoothStatus():`` in ``check_bluetooth_status`` by a second will solve this. Now, having sleep(1) is a bit ugly so it would probably be...

unpacking returns a tuple, quick fix for that. ```patch diff --git a/blueman/main/Manager.py b/blueman/main/Manager.py index dab76bd1..0277e93e 100644 --- a/blueman/main/Manager.py +++ b/blueman/main/Manager.py @@ -94,7 +94,8 @@ class Blueman(Gtk.Application): def on_applet_signal(_proxy: AppletService, _sender:...

The failure is a timing thing. After we call `SetBluetoothStatus` we immediately ask for the status which is not updated (yet). Adding a simple sleep(1) fixes the exit being called....