Skip to content

Keep the bar icon when rfkill powers the radio off - #6

Merged
ssupt merged 2 commits into
ssupt:mainfrom
Cdt85:fix/show-off-state-when-rfkill-removes-adapter
Oct 31, 2026
Merged

ssupt merged 2 commits into
ssupt:mainfrom
Cdt85:fix/show-off-state-when-rfkill-removes-adapter

Conversation

@Cdt85

@Cdt85 Cdt85 commented Oct 29, 2026 •

Copy link
Copy Markdown
Contributor
  • Keep the Bluetooth bar icon and power controls available when an rfkill software block removes the adapter from BlueZ, so Bluetooth can be turned back on from the widget, keyboard, or IPC.
  • Restart failed rfkill watchers with capped backoff, preserve the last known state between failures, and replace stale switch IDs when a fresh snapshot arrives. Stop watching when an adapter returns.
  • Track software and hardware blocks separately so a hardware-blocked radio is not presented as recoverable through the software power control.

Cdt85 and others added 2 commits October 29, 2026 06:37
On some laptops (Dell's dell-rfkill among them) the rfkill soft block that
omarchy-bluetooth-power uses for "off" cuts power to the Bluetooth chip. The
adapter then disappears from BlueZ instead of reading Powered: no, so the
widget hid itself and could not turn Bluetooth back on.

While BlueZ has no adapter, watch `rfkill event` and treat a soft-blocked
Bluetooth switch as off: the icon, status text and power switch stay, and
toggling runs omarchy-bluetooth-power on. The watcher only runs while the
adapter is missing and does not poll.

Rebuild the bundled service for the new Panel.qml and Model.js fingerprint.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@ssupt
ssupt merged commit 8d0c9b7 into ssupt:main Oct 31, 2026
2 checks passed
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.

2 participants