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 panel shows the device's raw hardware Name instead of the user-set Alias
Reported by diegovrocha · filed Sep 1, 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
What happened
Renaming a paired Bluetooth device (via bluetoothctl set-alias or setting
the BlueZ Alias D-Bus property directly) does not change what the
Bluetooth bar panel displays. It keeps showing the device's original
hardware-advertised name.
What was expected
The panel should show the custom alias, the same way GNOME/KDE Bluetooth
settings and bluetoothctl devices do — Alias is the whole point of a
user-facing rename.
Root cause
In shell/plugins/panels/bluetooth/Model.js, deviceLabel() is:
function deviceLabel(device) {
if (!device) return ""
return String(device.deviceName || device.name || "").trim()
}
device.name is Quickshell's Quickshell.Bluetooth.BluetoothDevice.name
— writable (setName), backed by BlueZ's Alias. device.deviceName is
the read-only property backed by BlueZ's raw Name. The function checksdeviceName first, so any device with a real hardware name (i.e. every
device that has ever had a human-readable name) always shows that instead
of a custom alias, because deviceName is never empty.
Suggested fix
Swap the priority:
return String(device.name || device.deviceName || "").trim()
Verified locally: cloning the plugin and applying this one-line swap
makes the panel correctly reflect the alias.
Steps to reproduce
- Pair a Bluetooth device that has its own hardware name (e.g. headphones).
bluetoothctl set-alias "My Custom Name"(or setAliasvia D-Bus).- Open the Bluetooth bar panel — the custom name never appears.
System
- Omarchy 4.0.1-1 (stable channel)
- quickshell 0.3.1-1
- Kernel 7.1.9-arch1-2
- CPU: 13th Gen Intel Core i9-13900H
- GPU: Intel Iris Xe (Raptor Lake-P)
View raw text
### What happened
Renaming a paired Bluetooth device (via `bluetoothctl set-alias` or setting
the BlueZ `Alias` D-Bus property directly) does not change what the
Bluetooth bar panel displays. It keeps showing the device's original
hardware-advertised name.
### What was expected
The panel should show the custom alias, the same way GNOME/KDE Bluetooth
settings and `bluetoothctl devices` do — Alias is the whole point of a
user-facing rename.
### Root cause
In `shell/plugins/panels/bluetooth/Model.js`, `deviceLabel()` is:
function deviceLabel(device) {
if (!device) return ""
return String(device.deviceName || device.name || "").trim()
}
`device.name` is Quickshell's `Quickshell.Bluetooth.BluetoothDevice.name`
— writable (`setName`), backed by BlueZ's `Alias`. `device.deviceName` is
the read-only property backed by BlueZ's raw `Name`. The function checks
`deviceName` first, so any device with a real hardware name (i.e. every
device that has ever had a human-readable name) always shows that instead
of a custom alias, because `deviceName` is never empty.
### Suggested fix
Swap the priority:
return String(device.name || device.deviceName || "").trim()
Verified locally: cloning the plugin and applying this one-line swap
makes the panel correctly reflect the alias.
### Steps to reproduce
1. Pair a Bluetooth device that has its own hardware name (e.g. headphones).
2. `bluetoothctl set-alias "My Custom Name"` (or set `Alias` via D-Bus).
3. Open the Bluetooth bar panel — the custom name never appears.
### System
- Omarchy 4.0.1-1 (stable channel)
- quickshell 0.3.1-1
- Kernel 7.1.9-arch1-2
- CPU: 13th Gen Intel Core i9-13900H
- GPU: Intel Iris Xe (Raptor Lake-P)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