Blueman's blacklist/block does not work completely

[SpiderUnderUrBed]

I have a speaker, sometimes I use it, sometimes other people in my house use it, to get it to work with linux is a very finnicky pairing process that works with other peoples laptops, but it is still being constantly connected and disconnected with blueman. The actual speaker working as it is, is probably not a blueman problem, what is a blueman problem is the fact that blocking/blacklisting a device does not disable the notifications

(using nix eval to get versions)
blueman: "2.4.6"
BlueZ: "5.84"
Distribution: Nixos 25.11 (Xantusia)
Desktop environment: KDE 6.5.5

General nix info:

 - system: `"x86_64-linux"`
 - host os: `Linux 6.12.76, NixOS, 25.11 (Xantusia), 25.11.20260313.3e20095`
 - multi-user?: `yes`
 - sandbox: `yes`
 - version: `nix-env (Nix) 2.31.2`
 - nixpkgs: `/nix/store/cy6cvjfw0729jx30b2khdbjak8wbbcs1-source`

Logs

[spiderunderurbed@daspidercave:~]$ blueman-applet --loglevel debug

(.blueman-applet-wrapped:648179): Gtk-WARNING **: 13:21:26.430: Unknown key Settings in /home/spiderunderurbed/.config/gtk-3.0/settings.ini
blueman-applet 13.21.26 INFO     PluginManager:86 load_plugin: ['AuthAgent', 'AutoConnect', 'ConnectionNotifier', 'DBusService', 'DhcpClient', 'DisconnectItems', 'DiscvManager', 'ExitItem', 'GameControllerWakelock', 'KillSwitch', 'Menu', 'NMDUNSupport', 'NMPANSupport', 'NetUsage', 'Networking', 'PPPSupport', 'PowerManager', 'PulseAudioProfile', 'RecentConns', 'SerialManager', 'ShowConnected', 'StandardItems', 'StatusIcon', 'StatusNotifierItem', 'TransferService']
blueman-applet 13.21.26 INFO     PluginManager:162 __load_plugin: loading <class 'blueman.plugins.applet.DBusService.DBusService'>
blueman-applet 13.21.26 INFO     PluginManager:162 __load_plugin: loading <class 'blueman.plugins.applet.Menu.Menu'>
blueman-applet 13.21.26 INFO     PluginManager:162 __load_plugin: loading <class 'blueman.plugins.applet.StandardItems.StandardItems'>
blueman-applet 13.21.26 INFO     PluginManager:162 __load_plugin: loading <class 'blueman.plugins.applet.StatusIcon.StatusIcon'>
blueman-applet 13.21.26 INFO     PluginManager:162 __load_plugin: loading <class 'blueman.plugins.applet.PowerManager.PowerManager'>
blueman-applet 13.21.26 INFO     PluginManager:162 __load_plugin: loading <class 'blueman.plugins.applet.RecentConns.RecentConns'>
blueman-applet 13.21.26 INFO     PluginManager:162 __load_plugin: loading <class 'blueman.plugins.applet.AuthAgent.AuthAgent'>
blueman-applet 13.21.26 INFO     PluginManager:162 __load_plugin: loading <class 'blueman.plugins.applet.AutoConnect.AutoConnect'>
blueman-applet 13.21.26 INFO     PluginManager:162 __load_plugin: loading <class 'blueman.plugins.applet.ConnectionNotifier.ConnectionNotifier'>
blueman-applet 13.21.26 WARNING  PluginManager:153 __load_plugin: Not loading DhcpClient because its conflict has higher priority
blueman-applet 13.21.26 INFO     PluginManager:162 __load_plugin: loading <class 'blueman.plugins.applet.DisconnectItems.DisconnectItems'>
blueman-applet 13.21.26 INFO     PluginManager:162 __load_plugin: loading <class 'blueman.plugins.applet.DiscvManager.DiscvManager'>
blueman-applet 13.21.26 INFO     PluginManager:162 __load_plugin: loading <class 'blueman.plugins.applet.ExitItem.ExitItem'>
blueman-applet 13.21.26 INFO     PluginManager:162 __load_plugin: loading <class 'blueman.plugins.applet.GameControllerWakelock.GameControllerWakelock'>
blueman-applet 13.21.26 INFO     PluginManager:162 __load_plugin: loading <class 'blueman.plugins.applet.KillSwitch.KillSwitch'>
blueman-applet 13.21.26 INFO     PluginManager:162 __load_plugin: loading <class 'blueman.plugins.applet.NMDUNSupport.NMDUNSupport'>
blueman-applet 13.21.26 INFO     PluginManager:162 __load_plugin: loading <class 'blueman.plugins.applet.NMPANSupport.NMPANSupport'>
blueman-applet 13.21.26 WARNING  PluginManager:153 __load_plugin: Not loading PPPSupport because its conflict has higher priority
blueman-applet 13.21.26 INFO     PluginManager:162 __load_plugin: loading <class 'blueman.plugins.applet.Networking.Networking'>
blueman-applet 13.21.26 INFO     PluginManager:162 __load_plugin: loading <class 'blueman.plugins.applet.PulseAudioProfile.AudioProfiles'>
blueman-applet 13.21.26 INFO     PulseAudioUtils:207 pa_context_event: 1
blueman-applet 13.21.26 INFO     PluginManager:162 __load_plugin: loading <class 'blueman.plugins.applet.SerialManager.SerialManager'>
blueman-applet 13.21.26 INFO     PluginManager:162 __load_plugin: loading <class 'blueman.plugins.applet.ShowConnected.ShowConnected'>
blueman-applet 13.21.26 INFO     PluginManager:162 __load_plugin: loading <class 'blueman.plugins.applet.StatusNotifierItem.StatusNotifierItem'>
blueman-applet 13.21.26 INFO     PluginManager:162 __load_plugin: loading <class 'blueman.plugins.applet.TransferService.TransferService'>
blueman-applet 13.21.26 INFO     PulseAudioUtils:207 pa_context_event: 2
blueman-applet 13.21.26 INFO     KillSwitch:106 io_event  : killswitch registered 1
blueman-applet 13.21.26 INFO     KillSwitch:122 io_event  : State: True
blueman-applet 13.21.26 INFO     PowerManager:161 update_power_state: off False | foff False | on True | current state True | new state True
blueman-applet 13.21.26 INFO     KillSwitch:85 _on_connman_vanished: net.connman vanished
blueman-applet 13.21.26 INFO     KillSwitch:106 io_event  : killswitch registered 5
blueman-applet 13.21.26 INFO     KillSwitch:122 io_event  : State: True
blueman-applet 13.21.26 INFO     PowerManager:161 update_power_state: off False | foff False | on True | current state True | new state True
blueman-applet 13.21.26 INFO     TransferService:233 _on_dbus_name_appeared: org.bluez.obex :1.36
blueman-applet 13.21.26 INFO     Applet:81 _on_dbus_name_appeared: org.bluez :1.6
blueman-applet 13.21.26 INFO     Functions:99 launch    : Gtk eventtime is 0, not using LaunchContext
blueman-applet 13.21.26 INFO     BluezAgent:56 register_agent: Register Agent
blueman-applet 13.21.26 INFO     RecentConns:113 notify    : <Device.Device object at 0x7f21a06e3700 (blueman+bluez+Device+Device at 0x56199e35ab50)> 00000000-0000-0000-0000-000000000000
blueman-applet 13.21.26 INFO     Networking:78 set_nap   : set nap False
blueman-applet 13.21.26 ERROR    AgentManager:20 on_register_failed: /org/bluez/obex/agent/blueman org.bluez.obex.Error.AlreadyExists Agent already exists
blueman-applet 13.21.26 INFO     ShowConnected:55 enumerate_connections: Found 1 existing connections
blueman-applet 13.21.26 INFO     PulseAudioUtils:207 pa_context_event: 3
blueman-applet 13.21.26 INFO     PulseAudioUtils:207 pa_context_event: 4
blueman-applet 13.21.26 INFO     PulseAudioProfile:135 on_pa_ready: PulseAudio Ready
blueman-applet 13.21.26 INFO     PulseAudioUtils:213 <lambda>  : 1
blueman-applet 13.21.28 DEBUG    Base:67 _properties_changed: /org/bluez/hci0/dev_40_9F_38_C8_EE_48 {'Connected': True} [] <Device.Device object at 0x7f21a06e3700 (blueman+bluez+Device+Device at 0x56199e35ab50)>
blueman-applet 13.21.31 INFO     PulseAudioUtils:337 __event_callback: 25 1402
blueman-applet 13.21.31 DEBUG    PulseAudioProfile:111 on_pa_event: 25 1402
blueman-applet 13.21.31 INFO     PulseAudioProfile:124 on_pa_event: card
blueman-applet 13.21.31 INFO     PulseAudioProfile:126 on_pa_event: change
blueman-applet 13.21.32 INFO     Notification:248 do_g_signal: 1
blueman-applet 13.21.32 DEBUG    Notification:252 do_g_signal: The notification expired.

bluetoothd:

[spiderunderurbed@daspidercave:~]$ systemctl status bluetooth
● bluetooth.service - Bluetooth service
     Loaded: loaded (/etc/systemd/system/bluetooth.service; enabled; preset: ignored)
    Drop-In: /nix/store/29y0czdq66f9xkm8632bh0wawdsjs1q0-system-units/bluetooth.service.d
             └─overrides.conf
     Active: active (running) since Thu 2026-04-02 21:10:16 NZDT; 1 day 16h ago
 Invocation: 6b29b82f181a4c25b79d4f846ed1e7cc
       Docs: man:bluetoothd(8)
   Main PID: 1264 (bluetoothd)
     Status: "Running"
         IP: 0B in, 0B out
         IO: 15M read, 18.6M written
      Tasks: 1 (limit: 18782)
     Memory: 6.1M (peak: 6.4M, swap: 588K, swap peak: 640K)
        CPU: 3.398s
     CGroup: /system.slice/bluetooth.service
             └─1264 /nix/store/6zhdw12swdpvg4vh5b9yv0nl9qbq0aq9-bluez-5.84/libexec/bluetooth/bluetoothd -f /etc/bluetooth/main.conf

Apr 04 13:13:38 daspidercave bluetoothd[1264]: src/device.c:search_cb() 40:9F:38:C8:EE:48: error updating services: Connection timed out (110)
Apr 04 13:14:40 daspidercave bluetoothd[1264]: src/device.c:search_cb() 40:9F:38:C8:EE:48: error updating services: Connection timed out (110)
Apr 04 13:15:01 daspidercave bluetoothd[1264]: src/device.c:search_cb() 40:9F:38:C8:EE:48: error updating services: Host is down (112)
Apr 04 13:16:38 daspidercave bluetoothd[1264]: src/device.c:search_cb() 40:9F:38:C8:EE:48: error updating services: Connection timed out (110)
Apr 04 13:17:01 daspidercave bluetoothd[1264]: src/device.c:search_cb() 40:9F:38:C8:EE:48: error updating services: Host is down (112)
Apr 04 13:18:01 daspidercave bluetoothd[1264]: src/device.c:search_cb() 40:9F:38:C8:EE:48: error updating services: Host is down (112)
Apr 04 13:19:01 daspidercave bluetoothd[1264]: src/device.c:search_cb() 40:9F:38:C8:EE:48: error updating services: Host is down (112)
Apr 04 13:20:36 daspidercave bluetoothd[1264]: src/device.c:search_cb() 40:9F:38:C8:EE:48: error updating services: Connection timed out (110)
Apr 04 13:22:10 daspidercave bluetoothd[1264]: src/device.c:search_cb() 40:9F:38:C8:EE:48: error updating services: Connection timed out (110)
Apr 04 13:22:31 daspidercave bluetoothd[1264]: src/device.c:search_cb() 40:9F:38:C8:EE:48: error updating services: Host is down (112)

[spiderunderurbed@daspidercave:~]$ 

[cschramm]

#3281 suppresses the notifications, but on second thought and some more research, I am not convinced that a blocked device can actually cause them.

The logs rather suggest that you do have the device on auto-connect. What seems to happen is that AutoConnect regularly tries to connect to the device and the device responds to the connection attempts, so that it technically becomes connected. It disconnects during discovery, though, as it is already used by a different device.

All that is independent of the blocked state. Blocking a device means that the kernel would reject connection attempts from the device.

There are basically two options to avoid the notifications in this situation: Either disable auto-connect for the device or disable the ConnectionNotifier plugin.