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 can't be turned back on from the bar on ThinkPads: rfkill block removes the adapter
Reported by madsclaussen · filed Oct 12, 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
System details
- Machine: Lenovo ThinkPad T460s (20FAS53900)
- CPU: Intel Core i5-6200U (integrated graphics)
- Omarchy: 4.0.4-1
- Kernel: 7.2.5-3-omarchy
- Quickshell: 0.3.1-1
What happens
On ThinkPads, turning Bluetooth off from the bar works, but it can't be turned back on from the bar. The Bluetooth icon also disappears from the bar.
Why
omarchy-bluetooth-power off runs rfkill block bluetooth, which blocks every Bluetooth rfkill switch, including thinkpad_acpi's tpacpi_bluetooth_sw. On ThinkPads that switch cuts power to the Bluetooth chip, so hci0 is removed entirely instead of just being set to Powered: no:
$ rfkill list # after turning Bluetooth off from the bar
0: tpacpi_bluetooth_sw: Bluetooth
Soft blocked: yes
Hard blocked: no
2: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
$ bluetoothctl list # (empty)Then, in shell/plugins/panels/bluetooth/Panel.qml:
toggleBluetooth()starts withif (!adapter) return, so the right-click toggle, the panel switch and thebkey do nothing once the adapter is gone.- The power switch has
visible: !!root.adapter, so it is hidden. iconreturns""when there is no adapter, so the bar icon disappears.
The panel offers no way to turn Bluetooth back on. Running omarchy-bluetooth-power on or rfkill unblock bluetooth from a terminal brings the adapter back right away.
Steps to reproduce
- On a ThinkPad with
thinkpad_acpiloaded, check thatrfkill listshowstpacpi_bluetooth_sw. - Turn Bluetooth off from the bar (right-click the icon, or use the switch in the panel).
- The bar icon disappears,
bluetoothctl listis empty, and nothing in the bar turns Bluetooth back on.
Expected
Bluetooth can be turned back on from the bar, and the bar shows an "off" icon instead of nothing.
Workaround / suggested fix
A no-adapter state that coexists with an rfkill soft block should be treated as "off". I'm running a clone with these changes, and off/on works repeatedly from the bar:
- if (!adapter) return ""
+ if (!adapter) return ""
...
- if (!adapter) return "No adapter"
+ if (!adapter) return "Turned Off"
...
- if (!adapter) return
- Quickshell.execDetached(["omarchy-bluetooth-power", adapter.enabled ? "off" : "on"])
+ Quickshell.execDetached(["omarchy-bluetooth-power", adapter && adapter.enabled ? "off" : "on"])
...
- visible: !!root.adapterA more careful version would show "off" only when a Bluetooth rfkill switch is actually soft-blocked, and keep "No adapter" for machines that really have none.
View raw text
## System details - **Machine:** Lenovo ThinkPad T460s (20FAS53900) - **CPU:** Intel Core i5-6200U (integrated graphics) - **Omarchy:** 4.0.4-1 - **Kernel:** 7.2.5-3-omarchy - **Quickshell:** 0.3.1-1 ## What happens On ThinkPads, turning Bluetooth off from the bar works, but it can't be turned back on from the bar. The Bluetooth icon also disappears from the bar. ## Why `omarchy-bluetooth-power off` runs `rfkill block bluetooth`, which blocks every Bluetooth rfkill switch, including `thinkpad_acpi`'s `tpacpi_bluetooth_sw`. On ThinkPads that switch cuts power to the Bluetooth chip, so `hci0` is removed entirely instead of just being set to `Powered: no`: ``` $ rfkill list # after turning Bluetooth off from the bar 0: tpacpi_bluetooth_sw: Bluetooth Soft blocked: yes Hard blocked: no 2: phy0: Wireless LAN Soft blocked: no Hard blocked: no $ bluetoothctl list # (empty) ``` Then, in `shell/plugins/panels/bluetooth/Panel.qml`: - `toggleBluetooth()` starts with `if (!adapter) return`, so the right-click toggle, the panel switch and the `b` key do nothing once the adapter is gone. - The power switch has `visible: !!root.adapter`, so it is hidden. - `icon` returns `""` when there is no adapter, so the bar icon disappears. The panel offers no way to turn Bluetooth back on. Running `omarchy-bluetooth-power on` or `rfkill unblock bluetooth` from a terminal brings the adapter back right away. ## Steps to reproduce 1. On a ThinkPad with `thinkpad_acpi` loaded, check that `rfkill list` shows `tpacpi_bluetooth_sw`. 2. Turn Bluetooth off from the bar (right-click the icon, or use the switch in the panel). 3. The bar icon disappears, `bluetoothctl list` is empty, and nothing in the bar turns Bluetooth back on. ## Expected Bluetooth can be turned back on from the bar, and the bar shows an "off" icon instead of nothing. ## Workaround / suggested fix A no-adapter state that coexists with an rfkill soft block should be treated as "off". I'm running a clone with these changes, and off/on works repeatedly from the bar: ```diff - if (!adapter) return "" + if (!adapter) return "" ... - if (!adapter) return "No adapter" + if (!adapter) return "Turned Off" ... - if (!adapter) return - Quickshell.execDetached(["omarchy-bluetooth-power", adapter.enabled ? "off" : "on"]) + Quickshell.execDetached(["omarchy-bluetooth-power", adapter && adapter.enabled ? "off" : "on"]) ... - visible: !!root.adapter ``` A more careful version would show "off" only when a Bluetooth rfkill switch is actually soft-blocked, and keep "No adapter" for machines that really have none.
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-12 06:36 UTC