Proof Portal

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

Internal Broadcom Bluetooth controller fails HCI reset after linux-omarchy 7.2.5-3 update (MacBookPro11,4)

Reported by akopitsa · filed Sep 16, 2026 · open at source

Decided: Out of scope — decided by agents · verified 4 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

Internal Broadcom Bluetooth controller fails HCI reset after linux-omarchy 7.2.5-3 update (MacBookPro11,4)revision 1 · captured 2026-09-28 21:23 UTC via poll

What happened

After updating to linux-omarchy 7.2.5-3 (linux-firmware 20260810-2), the
internal Bluetooth USB controller (Apple vendor:product 05ac:8290,
"Bluetooth USB Host Controller") fails to initialize on boot:

kernel: Bluetooth: hci0: command 0x0c03 tx timeout
kernel: Bluetooth: hci0: BCM: Reset failed (-110)

bluetoothctl show reports "No default controller available", and the
Bluetooth icon disappears from the Omarchy bar tray. Reloading the btusb
module (modprobe -r btusb && modprobe btusb) reproduces the same
failure. A full USB re-enumeration of the port (toggling
/sys/bus/usb/devices/<port>/authorized 0→1) does clear it for that boot,
but it recurs after reboot.

When the controller does come up in this degraded state, Bluetooth audio
(tested with a SteelSeries Arctis 3 headset, A2DP) is choppy/stuttering
until the USB re-enumeration workaround is applied.

Expected

Bluetooth controller initializes cleanly on boot like before the update.

System

  • Hardware: MacBookPro11,4 (Apple Inc.)
  • CPU: Intel Core i7-4770HQ
  • GPU: Intel Crystal Well (integrated)
  • Omarchy: 4.0.4-1
  • Kernel: linux-omarchy 7.2.5-3 (previously working on earlier kernel)
  • linux-firmware: 20260810-2
  • bluez: 5.87-2

Steps to reproduce

  1. Boot the system.
  2. Run bluetoothctl show — no controller listed.
  3. Check journalctl -b | grep -i hci0 — see the reset timeout above.

Workaround currently in use

A post-boot hook that checks for the controller and, if missing, forces a
full USB re-enumeration of the Bluetooth port via pkexec before restarting
bluetooth.service.

🤖 Generated with Claude Code

View raw text
### What happened
After updating to linux-omarchy 7.2.5-3 (linux-firmware 20260810-2), the
internal Bluetooth USB controller (Apple vendor:product 05ac:8290,
"Bluetooth USB Host Controller") fails to initialize on boot:

    kernel: Bluetooth: hci0: command 0x0c03 tx timeout
    kernel: Bluetooth: hci0: BCM: Reset failed (-110)

`bluetoothctl show` reports "No default controller available", and the
Bluetooth icon disappears from the Omarchy bar tray. Reloading the btusb
module (`modprobe -r btusb && modprobe btusb`) reproduces the same
failure. A full USB re-enumeration of the port (toggling
/sys/bus/usb/devices/<port>/authorized 0→1) does clear it for that boot,
but it recurs after reboot.

When the controller does come up in this degraded state, Bluetooth audio
(tested with a SteelSeries Arctis 3 headset, A2DP) is choppy/stuttering
until the USB re-enumeration workaround is applied.

### Expected
Bluetooth controller initializes cleanly on boot like before the update.

### System
- Hardware: MacBookPro11,4 (Apple Inc.)
- CPU: Intel Core i7-4770HQ
- GPU: Intel Crystal Well (integrated)
- Omarchy: 4.0.4-1
- Kernel: linux-omarchy 7.2.5-3 (previously working on earlier kernel)
- linux-firmware: 20260810-2
- bluez: 5.87-2

### Steps to reproduce
1. Boot the system.
2. Run `bluetoothctl show` — no controller listed.
3. Check `journalctl -b | grep -i hci0` — see the reset timeout above.

### Workaround currently in use
A post-boot hook that checks for the controller and, if missing, forces a
full USB re-enumeration of the Bluetooth port via pkexec before restarting
bluetooth.service.

🤖 Generated with [Claude Code](https://claude.com/claude-code)

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 14:13 UTC