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.
brcmfmac wedges NetworkManager+wpa_supplicant into unkillable D-state, aborting suspend
Reported by rand0mdud3 · filed Sep 11, 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
Hardware
MacBookPro11,5 (2015, pre-T2), BCM43602 14e4:43ba via brcmfmac, kernel 7.2.3-arch1-3, Omarchy 4.x. The #10332 sleep hook was installed but never ran here -- suspend aborted before hooks.
Sequence (single boot, timestamps from journal)
- 14:41:16 -- one warning, the only one:
brcmf_cfg80211_get_tx_power: error (-5) - 14:41:17 -- freeze starts on a systemctl suspend path
- 14:41:37 --
Freezing user space processes failed after 20.002 seconds (2 tasks refusing to freeze, wq_busy=0): NetworkManager (785) and wpa_supplicant (881), both state D inside the driver - Suspend aborted (
Failed to put system to sleep); machine stayed awake with dead Wi-Fi (iwhangs) - Reboot: user@1000, avahi, wpa_supplicant, NetworkManager all survive final SIGKILL (D-state, unkillable by design); /home and /tmp fail to unmount
- Hard poweroff required; first reboot froze before the splash with no journal; second booted clean, btrfs device stats zero errors
Why this is its own issue
Distinct signature from #10332's timeout cascade (no msgbuf timeouts here -- one -5, then wedge). Whether the wedge was spontaneous or triggered by freeze initiation at that exact second is unknowable from the logs; both readings are consistent. Either way the outcome class matters: a wifi firmware hiccup escalates to SIGKILL-proof processes, failed unmounts, and a hard poweroff -- there is no graceful recovery short of a driver reload done before the wedge (modprobe -r cycle works fine while the stack is healthy).
View raw text
## Hardware MacBookPro11,5 (2015, pre-T2), BCM43602 14e4:43ba via brcmfmac, kernel 7.2.3-arch1-3, Omarchy 4.x. The #10332 sleep hook was installed but never ran here -- suspend aborted before hooks. ## Sequence (single boot, timestamps from journal) - 14:41:16 -- one warning, the only one: `brcmf_cfg80211_get_tx_power: error (-5)` - 14:41:17 -- freeze starts on a systemctl suspend path - 14:41:37 -- `Freezing user space processes failed after 20.002 seconds (2 tasks refusing to freeze, wq_busy=0)`: NetworkManager (785) and wpa_supplicant (881), both state D inside the driver - Suspend aborted (`Failed to put system to sleep`); machine stayed awake with dead Wi-Fi (`iw` hangs) - Reboot: user@1000, avahi, wpa_supplicant, NetworkManager all survive final SIGKILL (D-state, unkillable by design); /home and /tmp fail to unmount - Hard poweroff required; first reboot froze before the splash with no journal; second booted clean, btrfs device stats zero errors ## Why this is its own issue Distinct signature from #10332's timeout cascade (no msgbuf timeouts here -- one -5, then wedge). Whether the wedge was spontaneous or triggered by freeze initiation at that exact second is unknowable from the logs; both readings are consistent. Either way the outcome class matters: a wifi firmware hiccup escalates to SIGKILL-proof processes, failed unmounts, and a hard poweroff -- there is no graceful recovery short of a driver reload done before the wedge (modprobe -r cycle works fine while the stack is healthy).
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 12:00 UTC