Proof Portal
Omarchy
ProbeLabs65 findings · 95 requirementsA proof layer — requirements, tests and verified fixes — for two of Omarchy's subsystems: the application menu (launcher scripts, QML model, JSONC config, search and selection) and the lock screen (lock scripts, QML, PAM authentication). Scope is deliberately limited to those components of omacom/omarchy; the rest of the distribution is not covered.
Bluetooth panel cannot re-enable an rfkill-blocked adapter
Reported by jimbosbagoftricks · filed Sep 1, 2026Closed upstream on 2026-09-20 by bjarneo via an automated message, as a duplicate of #6956 (R-4603). GitHub close reason: completed.
At a glance
- 1 · What is claimed?
- Only the report text below — no validator has restated it as checkable claims yet.
- 2 · What does it affect?
- Not yet mapped to any requirement or component.
- 3 · Is it reproducible?
- No validation has been run yet.
- 4 · What remains unclear?
- Not validated yet: no claims, no reproducer.
- 5 · What happens next?
- Our staff decide whether the report is valid. Where this project allows it, agents decide whether it duplicates another report or a known issue. No decision has been recorded yet.
Original report
What happened
Turning Bluetooth off from Omarchy's Bluetooth panel calls , which correctly uses to persist the off state. On this ThinkPad, that causes BlueZ/Quickshell to report no default adapter.
At that point the same panel displays , but offers no way to turn Bluetooth back on. The radio can only be recovered from a terminal with Unblocking bluetooth...
0: tpacpi_bluetooth_sw: Bluetooth
Soft blocked: no
Hard blocked: no (or Place your right index finger on the fingerprint reader
Verification timed out).
Steps to reproduce
- Start with Bluetooth on and a visible adapter.
- Open Omarchy's Bluetooth panel.
- Turn Bluetooth off using its on/off switch.
- Reopen the panel.
Expected behavior
The panel should retain an enabled control to turn Bluetooth back on, even while rfkill makes the BlueZ adapter unavailable.
Actual behavior
The panel reports and its switch is hidden, creating a dead end in the UI.
Cause and suggested fix
In , returns immediately when is null, and the is only visible when . When rfkill blocks the radio, both conditions prevent recovery.
A local user-plugin workaround that works is:
Environment
- Omarchy: 4.0.1-1
- Hardware: ThinkPad P1 Gen 2
- Bluetooth service remained active and enabled
- 0: tpacpi_bluetooth_sw: Bluetooth
Soft blocked: no
Hard blocked: no
4: hci0: Bluetooth
Soft blocked: no
Hard blocked: no after turning it off showed , .
View raw text
## What happened Turning Bluetooth off from Omarchy's Bluetooth panel calls , which correctly uses to persist the off state. On this ThinkPad, that causes BlueZ/Quickshell to report no default adapter. At that point the same panel displays , but offers no way to turn Bluetooth back on. The radio can only be recovered from a terminal with Unblocking bluetooth... 0: tpacpi_bluetooth_sw: Bluetooth Soft blocked: no Hard blocked: no (or Place your right index finger on the fingerprint reader Verification timed out). ## Steps to reproduce 1. Start with Bluetooth on and a visible adapter. 2. Open Omarchy's Bluetooth panel. 3. Turn Bluetooth off using its on/off switch. 4. Reopen the panel. ## Expected behavior The panel should retain an enabled control to turn Bluetooth back on, even while rfkill makes the BlueZ adapter unavailable. ## Actual behavior The panel reports and its switch is hidden, creating a dead end in the UI. ## Cause and suggested fix In , returns immediately when is null, and the is only visible when . When rfkill blocks the radio, both conditions prevent recovery. A local user-plugin workaround that works is: ## Environment - Omarchy: 4.0.1-1 - Hardware: ThinkPad P1 Gen 2 - Bluetooth service remained active and enabled - 0: tpacpi_bluetooth_sw: Bluetooth Soft blocked: no Hard blocked: no 4: hci0: Bluetooth Soft blocked: no Hard blocked: no after turning it off showed , .
Validation
Not checked yet. A validator will restate this report as checkable claims, map it to the project's requirements and write a reproducer that the proof engine runs.
Linked
Not linked to any known issue, other report or change yet.
Decision
Decisions are recorded by our staff — or, where this project allows it, by agents: checked by a second, independent agent, or by a single agent where the project's policy says so. Any decision reached so far is shown below.
No decision has been recorded yet.