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.
BCM4360: Wi-Fi goes dark, toggle won't recover it
Reported by in0vik · filed Sep 14, 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
MacBook Air (2017), i5-5350U / HD 6000, BCM4360 [14e4:43a0]. Omarchy 4.0.2-1, Linux 7.1.9-arch1-2, broadcom-wl 6.30.223.271-722, NetworkManager 1.58.1-1.
What's wrong?
Wi-Fi has died twice in three days on this always-on Mac. Still says connected, but gateway pings get 100% loss. Toggling Wi-Fi leaves it stuck disconnected. Reboot brings it back.
Latest hit was after ~51h uptime. Sleep and Wi-Fi power saving are off; the failure started before I opened the lid.
Reject scan trigger since one is already pending
WLC_SCAN error (-22)
CTRL-EVENT-SCAN-FAILED ret=-22Expected it to stay online, or at least recover without a reboot. No reliable repro beyond leaving it connected. Added failure snapshots to catch the next hit.
Looks similar to discussion #6401, but I haven't pinned down the root cause.
View raw text
### System details MacBook Air (2017), i5-5350U / HD 6000, BCM4360 `[14e4:43a0]`. Omarchy `4.0.2-1`, Linux `7.1.9-arch1-2`, broadcom-wl `6.30.223.271-722`, NetworkManager `1.58.1-1`. ### What's wrong? Wi-Fi has died twice in three days on this always-on Mac. Still says connected, but gateway pings get 100% loss. Toggling Wi-Fi leaves it stuck disconnected. Reboot brings it back. Latest hit was after ~51h uptime. Sleep and Wi-Fi power saving are off; the failure started before I opened the lid. ```text Reject scan trigger since one is already pending WLC_SCAN error (-22) CTRL-EVENT-SCAN-FAILED ret=-22 ``` Expected it to stay online, or at least recover without a reboot. No reliable repro beyond leaving it connected. Added failure snapshots to catch the next hit. Looks similar to [discussion #6401](https://github.com/omacom/omarchy/discussions/6401), but I haven't pinned down the root cause.
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 13:31 UTC