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-1118GitHub issuePublicDecided· Out of scope

Bluetooth bar toggle can remain visually off after resume while adapter is powered

Reported by Matt1656 · filed Sep 1, 2026 · open at source

Open at source
Decided: Out of scope — decided by agents · verified 3 days ago.

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

Bluetooth bar toggle can remain visually off after resume while adapter is poweredrevision 1 · captured 2026-09-28 21:24 UTC via poll

System details

  • AMD Ryzen 5 PRO 2500U with Radeon Vega Mobile Graphics
  • Intel Wireless-AC 9260 Bluetooth adapter
  • Omarchy 4.0.0-1
  • quickshell-git 0.3.0.r20.g28771c7-1
  • BlueZ / bluez-utils 5.87-2
  • Linux 7.1.8-arch1-3

What's wrong?

After a suspend/resume cycle, the omarchy.bluetooth widget in the top bar appeared to remain off and its on/off control did not visually update. Repeated attempts to turn Bluetooth on through the widget kept invoking the on path, even though Bluetooth was already fully enabled at the system level.

Observed state while the widget appeared off:

bluetooth.service: active (running)
rfkill: Soft blocked: no, Hard blocked: no
bluetoothctl show: Powered: yes, PowerState: on

The user journal showed many repeated calls from the bar interaction within a few seconds:

rfkill: unblock set for type bluetooth

No corresponding Bluetooth or Quickshell error was logged. The adapter was detected normally and bluetoothctl could query it. This suggests the Quickshell Bluetooth model/widget retained stale adapter.enabled state after resume, so toggleBluetooth() repeatedly selected omarchy-bluetooth-power on instead of reflecting or toggling the live BlueZ state.

The suspend/resume occurred shortly before the problem. BlueZ re-registered its audio endpoints successfully after resume.

Steps to reproduce

  1. Have Bluetooth enabled and the omarchy.bluetooth widget in the top bar.
  2. Suspend and resume the machine.
  3. Open the Bluetooth bar panel and try its on/off control.
  4. Observe that the widget may remain visually off and repeatedly call the on path despite bluetoothctl show reporting Powered: yes.

Expected behavior

The bar widget should refresh from the current BlueZ adapter state after resume and show Bluetooth as enabled. Each toggle action should use the live state rather than repeatedly issuing rfkill unblock bluetooth.

I have not included the full omarchy debug output because it contains unrelated machine details, but can provide targeted diagnostics if needed.

View raw text
### System details

- AMD Ryzen 5 PRO 2500U with Radeon Vega Mobile Graphics
- Intel Wireless-AC 9260 Bluetooth adapter
- Omarchy 4.0.0-1
- quickshell-git 0.3.0.r20.g28771c7-1
- BlueZ / bluez-utils 5.87-2
- Linux 7.1.8-arch1-3

### What's wrong?

After a suspend/resume cycle, the `omarchy.bluetooth` widget in the top bar appeared to remain off and its on/off control did not visually update. Repeated attempts to turn Bluetooth on through the widget kept invoking the on path, even though Bluetooth was already fully enabled at the system level.

Observed state while the widget appeared off:

```text
bluetooth.service: active (running)
rfkill: Soft blocked: no, Hard blocked: no
bluetoothctl show: Powered: yes, PowerState: on
```

The user journal showed many repeated calls from the bar interaction within a few seconds:

```text
rfkill: unblock set for type bluetooth
```

No corresponding Bluetooth or Quickshell error was logged. The adapter was detected normally and `bluetoothctl` could query it. This suggests the Quickshell Bluetooth model/widget retained stale `adapter.enabled` state after resume, so `toggleBluetooth()` repeatedly selected `omarchy-bluetooth-power on` instead of reflecting or toggling the live BlueZ state.

The suspend/resume occurred shortly before the problem. BlueZ re-registered its audio endpoints successfully after resume.

### Steps to reproduce

1. Have Bluetooth enabled and the `omarchy.bluetooth` widget in the top bar.
2. Suspend and resume the machine.
3. Open the Bluetooth bar panel and try its on/off control.
4. Observe that the widget may remain visually off and repeatedly call the on path despite `bluetoothctl show` reporting `Powered: yes`.

### Expected behavior

The bar widget should refresh from the current BlueZ adapter state after resume and show Bluetooth as enabled. Each toggle action should use the live state rather than repeatedly issuing `rfkill unblock bluetooth`.

I have not included the full `omarchy debug` output because it contains unrelated machine details, but can provide targeted diagnostics if needed.

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:26 UTC