blueman icon indicating copy to clipboard operation
blueman copied to clipboard

Disabling ConnectionNotifier does not stop notifications

Open Ao1Pointblank opened this issue 3 months ago • 8 comments

Blueman 2.4.6 EndeavourOS CInnamon

As the title suggests, I am plagued with connection successful notifications which I cannot disable by unchecking the Connections Notifier plugin.

If there is a way to manually break this plugin, I would accept that as a solution.

Ao1Pointblank avatar Sep 01 '25 04:09 Ao1Pointblank

Disabling the plugin should indeed have the desired effect. What exact notification are you still getting?

cschramm avatar Sep 01 '25 07:09 cschramm

Image

Ao1Pointblank avatar Sep 01 '25 16:09 Ao1Pointblank

That is a different notification from the autoconnect plugin. You have this enabled on the audio device.

infirit avatar Sep 01 '25 16:09 infirit

Aha, thanks. I have to disable audio and input profiles checkbox? What exactly does that option do, anyway?

Ao1Pointblank avatar Sep 01 '25 21:09 Ao1Pointblank

Aha, thanks. I have to disable audio and input profiles checkbox? What exactly does that option do, anyway?

It tries to connect to that device and selected profile on set intervals, 60 seconds iirc.

infirit avatar Sep 02 '25 09:09 infirit

I have the exact same problem. I am running version 2.4.4 on Debian Trixie and despite having notification plugin turned off I still get notifications when connecting my wireless headphones:

Image

How do I disable that? Disabling automatic connection of "Audio and input profiles" is not a solution, because it breaks headphone functionality.

jstolarek avatar Sep 30 '25 08:09 jstolarek

I found a workaround: edit AutoConnect.py applet file, under Debian located in /usr/lib/python3/dist-packages/blueman/plugins/applet. Find the function responsible for the notification (line 65 in version 2.4.4):

def reply(dev: Optional[Device] = device, service_name: str = ServiceUUID(uuid).name) -> None:
    assert isinstance(dev, Device)  # https://github.com/python/mypy/issues/2608
    Notification(_("Connected"), _("Automatically connected to %(service)s on %(device)s") %
                 {"service": service_name, "device": dev.display_name},
                 icon_name=dev["Icon"]).show()

and comment out the three lines that display the notification:

def reply(dev: Optional[Device] = device, service_name: str = ServiceUUID(uuid).name) -> None:
    assert isinstance(dev, Device)  # https://github.com/python/mypy/issues/2608
    # Notification(_("Connected"), _("Automatically connected to %(service)s on %(device)s") %
    #              {"service": service_name, "device": dev.display_name},
    #              icon_name=dev["Icon"]).show()

A proper solution would be to route all notifications through ConnectionNotification plugin and have it make decisions whether a notification should be displayed or not.

jstolarek avatar Sep 30 '25 09:09 jstolarek

I found a workaround: edit AutoConnect.py applet file, under Debian located in /usr/lib/python3/dist-packages/blueman/plugins/applet. Find the function responsible for the notification (line 65 in version 2.4.4):

and comment out the three lines that display the notification:

def reply(dev: Optional[Device] = device, service_name: str = ServiceUUID(uuid).name) -> None: assert isinstance(dev, Device) # https://github.com/python/mypy/issues/2608 # Notification(_("Connected"), _("Automatically connected to %(service)s on %(device)s") % # {"service": service_name, "device": dev.display_name}, # icon_name=dev["Icon"]).show()

Thanks, this worked for me on Linux Mint.

Bezowski avatar Nov 26 '25 05:11 Bezowski