“Remove Device” button does nothing when Bluetooth adapter is soft-blocked (rfkill)

[Sylos-Creator]

Description:
When the Bluetooth adapter is soft-blocked (via rfkill), clicking Remove on a paired device in Blueman Manager has no effect. No error or feedback is shown, and the device remains listed.

Once the adapter is unblocked, the same Remove button works as expected and the device is deleted immediately.

This suggests that the D-Bus call to remove the device fails silently when the controller is not ready, and the GUI does not surface any error or notification.

Steps to Reproduce:

1. Ensure at least one device is paired and visible in Blueman.

2. Run:

   sudo rfkill block bluetooth

3. In Blueman Manager, select the device and click Remove.
   → Nothing happens.

4. Run:

   sudo rfkill unblock bluetooth

5. Click Remove again.
   → Device is removed successfully.

Expected Behavior:
Blueman should display an error message or notification when the adapter is powered off or blocked, instead of silently failing.

Environment:

• Distro: Linux Mint 22 (Ubuntu 24.04 base)

[infirit]

That error is not listed in the possible errors for RemoveDevice. I'll add that we prevent removal to #2821. Wait I misread, this is rfkill blocking.

blueman-manager 23.10.21 ERROR    Base:93 callback  : Unhandled error for org.bluez.Adapter1.RemoveDevice
Traceback (most recent call last):
  File "/usr/lib/python3.13/site-packages/blueman/bluez/Base.py", line 86, in callback
    value = proxy.call_finish(result).unpack()
            ~~~~~~~~~~~~~~~~~^^^^^^^^
gi.repository.GLib.GError: g-io-error-quark: GDBus.Error:org.bluez.Error.NotReady: Resource Not Ready (36)