[GH-ISSUE #247] [Linux] Permit Disabling Disconnect Notification #113

Closed
opened 2026-03-02 12:03:35 +03:00 by kerem · 1 comment
Owner

Originally created by @Ari-43 on GitHub (Nov 15, 2025).
Original GitHub issue: https://github.com/kavishdevar/librepods/issues/247

The Issue

Currently, the application displays its own notification when AirPods disconnect.

Redundant disconnect notification provided by this utility:
Image

Context

On Linux, Blueman or another Bluetooth manager (usually part of the desktop environment) often already sends a system notification to the running notification daemon when a Bluetooth device disconnects. For most users the baked-in notification provided by this application would be redundant or even annoying (may render above other desktop notifications, only partially respects system QT theme from my experience).

A disconnect notification from Blueman, my GUI Bluetooth manager, sent to xfce4-notifyd, the notification daemon I use:
Image

Potential Fix

Provide the the ability to select the utility's notification behavior from one of the following:

  • Disable Notifications
    • Should be the default
    • Blueman and many desktop environments already provide notifications for Bluetooth device disconnect events, so nothing is required from this utility in this regard
  • Send System Notification
    • May be useful for those who use a notification daemon, but don't use something like Blueman and still want a notification when their AirPods disconnect
    • Should be relatively simple to implement
  • Use baked-in notifications
    • Same as current behavior
    • Useful if a notification daemon is not running
Originally created by @Ari-43 on GitHub (Nov 15, 2025). Original GitHub issue: https://github.com/kavishdevar/librepods/issues/247 ## The Issue Currently, the application displays its own notification when AirPods disconnect. Redundant disconnect notification provided by this utility: <img width="377" height="76" alt="Image" src="https://github.com/user-attachments/assets/f459e1e1-cf55-4fe1-a97f-6269a7abcca0" /> ## Context On Linux, Blueman or another Bluetooth manager (usually part of the desktop environment) often already sends a system notification to the running notification daemon when a Bluetooth device disconnects. For most users the baked-in notification provided by this application would be redundant or even annoying (may render above other desktop notifications, only partially respects system QT theme from my experience). A disconnect notification from Blueman, my GUI Bluetooth manager, sent to `xfce4-notifyd`, the notification daemon I use: <img width="280" height="72" alt="Image" src="https://github.com/user-attachments/assets/c490c095-a8ae-43e6-904b-eb711a98b67c" /> ## Potential Fix Provide the the ability to select the utility's notification behavior from one of the following: - Disable Notifications - Should be the default - Blueman and many desktop environments already provide notifications for Bluetooth device disconnect events, so nothing is required from this utility in this regard - Send System Notification - May be useful for those who use a notification daemon, but don't use something like Blueman and still want a notification when their AirPods disconnect - Should be relatively simple to [implement](https://specifications.freedesktop.org/notification/latest/protocol.html) - Use baked-in notifications - Same as current behavior - Useful if a notification daemon is not running
kerem closed this issue 2026-03-02 12:03:36 +03:00
Author
Owner

@Ari-43 commented on GitHub (Nov 15, 2025):

I am blind, fully disabling the notification is already an option. Apologies. I do believe this should be the default behavior, but I'll consider this resolved since the option is present.

<!-- gh-comment-id:3535556063 --> @Ari-43 commented on GitHub (Nov 15, 2025): I am blind, fully disabling the notification is already an option. Apologies. I do believe this should be the default behavior, but I'll consider this resolved since the option is present.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/librepods#113
No description provided.