Proof Portal

Sign in
Project overview

Omarchy

ProbeLabs65 findings · 95 requirements

A 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.

Inbox
ReportR-4829GitHub issuePublicReceived

Bluetooth power-off is presented as “No adapter” and removes the control to turn it back on

Reported by sangjaepark0000 · filed Sep 2, 2026Closed upstream on 2026-09-20 by bjarneo via an automated message, as a duplicate of #6956 (R-4603). GitHub close reason: completed.

Open at source
Received and recorded verbatim. Nothing has been checked yet.

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

Bluetooth power-off is presented as “No adapter” and removes the control to turn it back onrevision 1 · captured 2026-10-04 12:03 UTC via poll

What happened

Turning Bluetooth off from the stock omarchy.bluetooth panel causes the panel to show No adapter instead of an off state.

The power switch then disappears, so Bluetooth cannot be turned back on from the panel.

Steps to reproduce

  1. Open the Bluetooth panel.
  2. With a working, powered-on adapter, use the panel power switch to turn Bluetooth off.
  3. Observe the panel.

Actual behavior

The panel shows:

  • No adapter
  • No Bluetooth adapter

The power switch is hidden.

Expected behavior

The UI should distinguish:

  • Adapter present and Bluetooth on
  • Adapter present and Bluetooth off
  • No adapter present

When Bluetooth is off, the panel should show an off state such as Turned Off and retain a control that can turn it back on. No adapter should be reserved for a genuinely absent adapter.

Notes

The panel power path invokes omarchy-bluetooth-power off, which persists the off state with rfkill block bluetooth. On this system, Quickshell then exposes no default Bluetooth adapter, and the panel treats that as physical adapter absence.

Environment:

  • Omarchy: 4.0.0.r1979.gb686ed8-1
  • Quickshell: 0.3.1-1
  • BlueZ: 5.87-2
  • Adapter: Intel 8087:0026
View raw text
## What happened

Turning Bluetooth off from the stock `omarchy.bluetooth` panel causes the panel to show **No adapter** instead of an off state.

The power switch then disappears, so Bluetooth cannot be turned back on from the panel.

## Steps to reproduce

1. Open the Bluetooth panel.
2. With a working, powered-on adapter, use the panel power switch to turn Bluetooth off.
3. Observe the panel.

## Actual behavior

The panel shows:

- `No adapter`
- `No Bluetooth adapter`

The power switch is hidden.

## Expected behavior

The UI should distinguish:

- Adapter present and Bluetooth on
- Adapter present and Bluetooth off
- No adapter present

When Bluetooth is off, the panel should show an off state such as `Turned Off` and retain a control that can turn it back on. `No adapter` should be reserved for a genuinely absent adapter.

## Notes

The panel power path invokes `omarchy-bluetooth-power off`, which persists the off state with `rfkill block bluetooth`. On this system, Quickshell then exposes no default Bluetooth adapter, and the panel treats that as physical adapter absence.

Environment:

- Omarchy: `4.0.0.r1979.gb686ed8-1`
- Quickshell: `0.3.1-1`
- BlueZ: `5.87-2`
- Adapter: Intel `8087:0026`

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.