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

Bluetooth panel shows "Turned Off" while adapter is powered and device connected (stale state after wake from sleep)

Reported by Bro-Kun · filed Sep 30, 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 panel shows "Turned Off" while adapter is powered and device connected (stale state after wake from sleep)revision 1 · captured 2026-09-30 01:46 UTC via poll

What happened

The Bluetooth panel in the Omarchy shell repeatedly shows "Turned Off" (hero toggle off + disabled icon) even though the adapter is powered on and a device is connected. The panel stays wrong until the shell is restarted with omarchy restart shell, which fixes it instantly.

State observed on the system while the panel was showing "Turned Off":

$ bluetoothctl show
	 Powered: yes
	 PowerState: on
$ bluetoothctl devices Connected
Device D6:35:70:D1:1B:D7 MX Ergo
$ rfkill list bluetooth
2: hci0: Bluetooth
	Soft blocked: no
	Hard blocked: no

Steps to reproduce

  1. Suspend the machine (s2idle). Most reliably reproduced after a long suspend (~78 h in the captured instance), but it has happened after shorter sleep sessions several times.
  2. Wake the machine; the paired device (Logitech MX Ergo) reconnects automatically.
  3. Open the Bluetooth panel: it shows "Turned Off" and the adapter toggle appears off, even though bluetoothctl reports Powered: yes and the device is connected.
  4. omarchy restart shell → panel immediately shows the correct powered/connected state.

Expected

The panel should reflect the actual BlueZ adapter state (powered, device connected), or recover after the missed state change.

Notes / likely cause

The panel binds readonly property var adapter: Bluetooth.defaultAdapter (plugins/panels/bluetooth/Panel.qml:24) and drives the hero text and icon off adapter.enabled (Panel.qml:60, 79). After wake-from-sleep this property appears to go stale — the BlueZ PropertiesChanged update is missed and the panel has no recovery path other than a full shell restart. This may ultimately be a Quickshell DBus subscription issue after suspend/resume, but from the user side the panel is the visible failure.

Workaround

omarchy restart shell

System details

  • Omarchy 4.0.4-1
  • Hyprland 0.56.2
  • Quickshell 0.3.1 (Arch package)
  • bluez 5.87-2
  • Kernel 7.2.5-3-omarchy
  • Hardware: Microsoft Surface Go (Intel Pentium 4415Y, HD Graphics 615), Wayland
View raw text
### What happened

The Bluetooth panel in the Omarchy shell repeatedly shows **"Turned Off"** (hero toggle off + disabled icon) even though the adapter is powered on and a device is connected. The panel stays wrong until the shell is restarted with `omarchy restart shell`, which fixes it instantly.

State observed on the system **while the panel was showing "Turned Off"**:

```
$ bluetoothctl show
	 Powered: yes
	 PowerState: on
$ bluetoothctl devices Connected
Device D6:35:70:D1:1B:D7 MX Ergo
$ rfkill list bluetooth
2: hci0: Bluetooth
	Soft blocked: no
	Hard blocked: no
```

### Steps to reproduce

1. Suspend the machine (s2idle). Most reliably reproduced after a long suspend (~78 h in the captured instance), but it has happened after shorter sleep sessions several times.
2. Wake the machine; the paired device (Logitech MX Ergo) reconnects automatically.
3. Open the Bluetooth panel: it shows "Turned Off" and the adapter toggle appears off, even though `bluetoothctl` reports `Powered: yes` and the device is connected.
4. `omarchy restart shell` → panel immediately shows the correct powered/connected state.

### Expected

The panel should reflect the actual BlueZ adapter state (powered, device connected), or recover after the missed state change.

### Notes / likely cause

The panel binds `readonly property var adapter: Bluetooth.defaultAdapter` (plugins/panels/bluetooth/Panel.qml:24) and drives the hero text and icon off `adapter.enabled` (Panel.qml:60, 79). After wake-from-sleep this property appears to go stale — the BlueZ `PropertiesChanged` update is missed and the panel has no recovery path other than a full shell restart. This may ultimately be a Quickshell DBus subscription issue after suspend/resume, but from the user side the panel is the visible failure.

### Workaround

`omarchy restart shell`

### System details

- Omarchy 4.0.4-1
- Hyprland 0.56.2
- Quickshell 0.3.1 (Arch package)
- bluez 5.87-2
- Kernel 7.2.5-3-omarchy
- Hardware: Microsoft Surface Go (Intel Pentium 4415Y, HD Graphics 615), Wayland

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 20:15 UTC