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 regression on kernel 7.2.x — Dell Precision 3590 (Broadcom 58200 / 0a5c:5864)
Reported by mprzyby2 · filed Sep 18, 2026Closed upstream on 2026-09-19 by its own reporter mprzyby2. GitHub close reason: completed. Closed by its own reporter — not by itself evidence of a fix.
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?
- Not yet mapped to any requirement or component.
- 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?
- Our staff decide whether the report is valid. Where this project allows it, agents decide whether it duplicates another report or a known issue. No decision has been recorded yet.
Original report
System details
Omarchy 4.0.3-1 Kernel: 7.2.3-arch1-3 / 7.2.5-3-omarchy (both broken) Hardware: Dell Precision 3590 Bluetooth adapter: Broadcom Corp 58200 (USB ID: 0a5c:5864)
What's wrong?
Bluetooth stops working after upgrading from kernel 7.1.9 to 7.2.x.
The adapter is visible in lsusb but btusb fails to load firmware with error -19 (ENODEV).
Symptoms
- No bluetooth icon in waybar
- bluetoothctl show → "No default controller available"
- lsusb shows the adapter: Bus 003 Device 075: ID 0a5c:5864 Broadcom Corp. 58200
- btusb attempts to load Intel firmware (intel/ibt-0180-0041.sfi) on this Broadcom chip and fails
dmesg output (kernel 7.2.x)
Bluetooth: hci0: Found device firmware: intel/ibt-0180-0041.sfi
Bluetooth: hci0: Failed to send firmware data (-19)
Bluetooth: hci0: sending frame failed (-19)
Bluetooth: hci0: FW download error recovery failed (-19)
Bluetooth: hci0: Failed to read MSFT supported features (-19)
Working kernel
Kernel 7.1.9-arch1-2 — Bluetooth works correctly.
Confirmed by booting snapshot from 2026-09-07.
Workaround
Booting from a 7.1.9 snapshot restores Bluetooth.
Steps to reproduce
1. Update Omarchy to latest (kernel 7.2.x)
2. Reboot
3. Bluetooth adapter not available
View raw text
### System details Omarchy 4.0.3-1 Kernel: 7.2.3-arch1-3 / 7.2.5-3-omarchy (both broken) Hardware: Dell Precision 3590 Bluetooth adapter: Broadcom Corp 58200 (USB ID: 0a5c:5864) ### What's wrong? Bluetooth stops working after upgrading from kernel 7.1.9 to 7.2.x. The adapter is visible in lsusb but btusb fails to load firmware with error -19 (ENODEV). **Symptoms** - No bluetooth icon in waybar - `bluetoothctl show` → "No default controller available" - `lsusb` shows the adapter: `Bus 003 Device 075: ID 0a5c:5864 Broadcom Corp. 58200` - btusb attempts to load Intel firmware (`intel/ibt-0180-0041.sfi`) on this Broadcom chip and fails **dmesg output (kernel 7.2.x)** Bluetooth: hci0: Found device firmware: intel/ibt-0180-0041.sfi Bluetooth: hci0: Failed to send firmware data (-19) Bluetooth: hci0: sending frame failed (-19) Bluetooth: hci0: FW download error recovery failed (-19) Bluetooth: hci0: Failed to read MSFT supported features (-19) **Working kernel** Kernel 7.1.9-arch1-2 — Bluetooth works correctly. Confirmed by booting snapshot from 2026-09-07. **Workaround** Booting from a 7.1.9 snapshot restores Bluetooth. **Steps to reproduce** 1. Update Omarchy to latest (kernel 7.2.x) 2. Reboot 3. Bluetooth adapter not available
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.
No decision has been recorded yet.