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 shows 'Turned Off' while adapter is actually powered on
Reported by nojaf · filed Sep 1, 2026 · open at source
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?
- AreaOutside the audited area· Decided by agents · verified
- 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?
- Decided by agents and verified by a second, independent agent — see the decision.
Original report
What happened
The Bluetooth panel in the Omarchy shell (top bar) showed the toggle in the off position with the status text "TURNED OFF", even though the Bluetooth adapter was actually powered on and working (paired device visible under "Paired").
Checked directly:
- rfkill list bluetooth → Soft blocked: no, Hard blocked: no
- bluetoothctl show → Powered: yes, PowerState: on
- systemctl status bluetooth → active and running
So the actual radio/adapter state was on, but the shell panel's cached adapter.enabled state (which drives the toggle switch and "Turned Off" label in Panel.qml) was stale and out of sync with BlueZ's real Powered property.
Running omarchy restart shell resolved the mismatch — the panel then correctly reflected the adapter as on.
What was expected
The Bluetooth panel toggle/status should always reflect the live BlueZ adapter Powered state, without needing a shell restart to resync.
Steps to reproduce
Not fully deterministic yet, but seen after a suspend/resume cycle:
1. System suspends and resumes (journal shows Controller resume with wake event 0x0 around the time this was noticed).
2. Open the Bluetooth panel from the top bar.
3. Panel shows "TURNED OFF" with paired devices still listed, despite the adapter actually being powered and functional.
4. omarchy restart shell fixes the display.
System details
- Omarchy version: 4.0.2-1
- Kernel: 7.1.9-arch1-2
- CPU: 12th Gen Intel Core i7-12700K
- GPU: NVIDIA GeForce RTX 3070 (nvidia driver)
Note
omarchy debug --no-sudo --print (referenced in current docs/tooling) is not a recognized command on this install (omarchy commands --all has no debug entry), so the standard diagnostic log couldn't be attached.
View raw text
## What happened The Bluetooth panel in the Omarchy shell (top bar) showed the toggle in the off position with the status text "TURNED OFF", even though the Bluetooth adapter was actually powered on and working (paired device visible under "Paired"). Checked directly: - `rfkill list bluetooth` → `Soft blocked: no`, `Hard blocked: no` - `bluetoothctl show` → `Powered: yes`, `PowerState: on` - `systemctl status bluetooth` → active and running So the actual radio/adapter state was on, but the shell panel's cached `adapter.enabled` state (which drives the toggle switch and "Turned Off" label in `Panel.qml`) was stale and out of sync with BlueZ's real `Powered` property. Running `omarchy restart shell` resolved the mismatch — the panel then correctly reflected the adapter as on. ## What was expected The Bluetooth panel toggle/status should always reflect the live BlueZ adapter `Powered` state, without needing a shell restart to resync. ## Steps to reproduce Not fully deterministic yet, but seen after a suspend/resume cycle: 1. System suspends and resumes (journal shows `Controller resume with wake event 0x0` around the time this was noticed). 2. Open the Bluetooth panel from the top bar. 3. Panel shows "TURNED OFF" with paired devices still listed, despite the adapter actually being powered and functional. 4. `omarchy restart shell` fixes the display. ## System details - Omarchy version: 4.0.2-1 - Kernel: 7.1.9-arch1-2 - CPU: 12th Gen Intel Core i7-12700K - GPU: NVIDIA GeForce RTX 3070 (nvidia driver) ## Note `omarchy debug --no-sudo --print` (referenced in current docs/tooling) is not a recognized command on this install (`omarchy commands --all` has no `debug` entry), so the standard diagnostic log couldn't be attached.
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.
- Out of scopeDecided by agents · verified · 2026-10-09 10:29 UTC