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

Bluetooth panel hides devices whose name was first cached as a MAC address (e.g. AirPods Max)

Reported by rade1701 · filed Sep 25, 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 hides devices whose name was first cached as a MAC address (e.g. AirPods Max)revision 1 · captured 2026-09-28 21:23 UTC via poll

What happened

AirPods Max in pairing mode (white blinking light) never appeared under Available in the bar's Bluetooth panel while scanning. After pairing them with bluetoothctl, they were connected and working, but still did not appear under Connected. They only showed up after omarchy restart shell.

Expected

The device should appear under Available once BlueZ has its real name, and under Connected once connected, without restarting the shell.

Steps to reproduce

  1. Have an Apple device nearby (AirPods Max) that BlueZ has already seen over BLE without a name. bluetoothctl devices lists it as Device 08:FF:44:4F:EE:C5 08-FF-44-4F-EE-C5.
  2. Put the AirPods in pairing mode and start a scan. BlueZ picks up the real name: Name: Rade’s AirPods Max - Find My.
  3. The Bluetooth panel still doesn't list the device under Available.
  4. Pair/trust/connect via bluetoothctl. BlueZ reports Name/Alias: Rade’s AirPods Max and Connected: yes. The panel still doesn't show it.
  5. omarchy restart shell: the device now appears under Connected.

Likely cause (not confirmed)

deviceLists() in shell/plugins/panels/bluetooth/Model.js skips any device where hasHumanName() is false. That includes names that look like addresses (isAddressLike), such as the 08-FF-44-4F-EE-C5 placeholder BlueZ uses for nameless devices. When BlueZ later updates Name/Alias, the panel doesn't seem to re-evaluate it. Either Quickshell's device name/deviceName isn't updated, or the deviceGroups binding doesn't re-run on name changes. So the device stays filtered out until the shell restarts.

System

  • Omarchy 4.0.4-1
  • quickshell 0.3.1-1
  • bluez 5.87-2
  • Kernel 7.2.3-arch1-3
View raw text
### What happened
AirPods Max in pairing mode (white blinking light) never appeared under **Available** in the bar's Bluetooth panel while scanning. After pairing them with `bluetoothctl`, they were connected and working, but still did not appear under **Connected**. They only showed up after `omarchy restart shell`.

### Expected
The device should appear under Available once BlueZ has its real name, and under Connected once connected, without restarting the shell.

### Steps to reproduce
1. Have an Apple device nearby (AirPods Max) that BlueZ has already seen over BLE without a name. `bluetoothctl devices` lists it as `Device 08:FF:44:4F:EE:C5 08-FF-44-4F-EE-C5`.
2. Put the AirPods in pairing mode and start a scan. BlueZ picks up the real name: `Name: Rade’s AirPods Max - Find My`.
3. The Bluetooth panel still doesn't list the device under Available.
4. Pair/trust/connect via `bluetoothctl`. BlueZ reports `Name`/`Alias: Rade’s AirPods Max` and `Connected: yes`. The panel still doesn't show it.
5. `omarchy restart shell`: the device now appears under Connected.

### Likely cause (not confirmed)
`deviceLists()` in `shell/plugins/panels/bluetooth/Model.js` skips any device where `hasHumanName()` is false. That includes names that look like addresses (`isAddressLike`), such as the `08-FF-44-4F-EE-C5` placeholder BlueZ uses for nameless devices. When BlueZ later updates `Name`/`Alias`, the panel doesn't seem to re-evaluate it. Either Quickshell's device `name`/`deviceName` isn't updated, or the `deviceGroups` binding doesn't re-run on name changes. So the device stays filtered out until the shell restarts.

### System
- Omarchy 4.0.4-1
- quickshell 0.3.1-1
- bluez 5.87-2
- Kernel 7.2.3-arch1-3

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 18:25 UTC