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.
bluez 5.87-2 ships a broken A2DP SEP cache (upstream regression, fix already in BlueZ master) — consider carrying the one-commit fix in the Omarchy repo
Reported by oskarth · filed Sep 24, 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
System details
Dell XPS 14 (2026), Intel CNVi Bluetooth 8086:e476 (btintel_pcie), kernel
7.2.5-3-omarchy, Omarchy 4.0.4, bluez 5.87-2 (current Arch package).
What's wrong?
BlueZ 5.87 ships upstream commit 912f5ef ("a2dp: Fix handling of codec
capability storage"), which added an i >= 2 condition to a loop that
starts at i = 0, so the loop body never runs and load_remote_sep()
discards every cached remote A2DP endpoint. Upstream fixed it three days
after the 5.87 release — b7d71e5
(https://github.com/bluez/bluez/commit/b7d71e5067856b0daf2f1f73b3fc95483236610e)
— but it is in no release, and Arch has not backported it.
Effects on 5.87-2:
- Every A2DP reconnect logs `profiles/audio/a2dp.c:load_remote_sep()
Unable to load LastUsed: rseid N not found` and runs a full AVDTP
discovery instead of the cached path. My current boot has 24 of these
for one headset (Bose QC Ultra 2nd Gen).
- For some headsets the reconnect comes up with no audio: device shows
connected, battery/AVRCP work, a2dp-sink profile connect fails with
"Device or resource busy". Upstream: bluez/bluez#2285 (closed by the
fix) and bluez/bluez#2321 (open). In #2321 an Omarchy user rebuilt
Arch's 5.87-2 PKGBUILD with b7d71e5 applied and confirmed it fixes
the no-audio on the same Bose model across repeated power cycles.
#8231 (autoconnected Bose speaker, silent until a manual
disconnect/reconnect) looks like the same class — that workaround is
exactly what the reporters in bluez#2321 describe.
Since Omarchy already ships its own packages through the Omarchy repo
(linux-omarchy), would you consider carrying bluez 5.87-2 plus b7d71e5
until Arch backports it or BlueZ cuts a release? It is a one-commit
patch on the stock PKGBUILD. Happy to test a build.
View raw text
### System details
Dell XPS 14 (2026), Intel CNVi Bluetooth 8086:e476 (btintel_pcie), kernel
7.2.5-3-omarchy, Omarchy 4.0.4, bluez 5.87-2 (current Arch package).
### What's wrong?
BlueZ 5.87 ships upstream commit 912f5ef ("a2dp: Fix handling of codec
capability storage"), which added an `i >= 2` condition to a loop that
starts at `i = 0`, so the loop body never runs and load_remote_sep()
discards every cached remote A2DP endpoint. Upstream fixed it three days
after the 5.87 release — b7d71e5
(https://github.com/bluez/bluez/commit/b7d71e5067856b0daf2f1f73b3fc95483236610e)
— but it is in no release, and Arch has not backported it.
Effects on 5.87-2:
- Every A2DP reconnect logs `profiles/audio/a2dp.c:load_remote_sep()
Unable to load LastUsed: rseid N not found` and runs a full AVDTP
discovery instead of the cached path. My current boot has 24 of these
for one headset (Bose QC Ultra 2nd Gen).
- For some headsets the reconnect comes up with no audio: device shows
connected, battery/AVRCP work, a2dp-sink profile connect fails with
"Device or resource busy". Upstream: bluez/bluez#2285 (closed by the
fix) and bluez/bluez#2321 (open). In #2321 an Omarchy user rebuilt
Arch's 5.87-2 PKGBUILD with b7d71e5 applied and confirmed it fixes
the no-audio on the same Bose model across repeated power cycles.
#8231 (autoconnected Bose speaker, silent until a manual
disconnect/reconnect) looks like the same class — that workaround is
exactly what the reporters in bluez#2321 describe.
Since Omarchy already ships its own packages through the Omarchy repo
(linux-omarchy), would you consider carrying bluez 5.87-2 plus b7d71e5
until Arch backports it or BlueZ cuts a release? It is a one-commit
patch on the stock PKGBUILD. Happy to test a build.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 17:45 UTC