Skip to content

Suppress notifications for blocked devices#3281

Merged
cschramm merged 1 commit into
blueman-project:mainfrom
cschramm:blocked-notifications
May 27, 2026
Merged

Suppress notifications for blocked devices#3281
cschramm merged 1 commit into
blueman-project:mainfrom
cschramm:blocked-notifications

Conversation

@cschramm
Copy link
Copy Markdown
Member

Closes #3197

@cschramm cschramm requested a review from infirit May 26, 2026 10:51
@cschramm cschramm enabled auto-merge (squash) May 26, 2026 10:56
@cschramm cschramm force-pushed the blocked-notifications branch from 78698f2 to 3b5cf49 Compare May 27, 2026 20:10
@sonarqubecloud
Copy link
Copy Markdown

Copy link
Copy Markdown
Contributor

@infirit infirit left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Slightly confused why blueman is getting a signal from bluez at all. It does not happen to me with my mi speaker 🤷 .

@cschramm cschramm merged commit 51cce53 into blueman-project:main May 27, 2026
28 of 29 checks passed
@infirit
Copy link
Copy Markdown
Contributor

infirit commented May 27, 2026

I have more fixes for blocked devices here #2821

cschramm added a commit to cschramm/blueman that referenced this pull request May 27, 2026
)"

I think that was completely misled. It targeted notifications for incoming connection attempts from blocked devices, which are mostly blocked by the kernel early on, so that no connection ever shows up (apart from very rare edge cases). What it actually suppresses, though, are notifications for any outgoing connection to blocked devices.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Blueman's blacklist/block does not work completely

2 participants