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.
BCM43602 on 2015–2017 Intel Macs associates but has no connectivity until iw reg set <country>
Reported by Clowdyffs · filed Sep 13, 2026Closed upstream on 2026-09-21 by bjarneo via an automated message, as a duplicate of #9019 (R-1244). GitHub close reason: completed.
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
Intel Macbook Pro 2017 (14,1), 16gb, omarchy 4.0.3-1
What's wrong?
After a fresh Omarchy installation, Wi-Fi showed as connected to my local network, but connectivity did not work. Pings timed out with 100% packet loss, and I could not download system updates.
Running the following restored connectivity:
sudo iw reg set USExpected behavior: Wi-Fi connectivity should work after installation without manually setting the regulatory domain.
Could the installer ensure that the appropriate country-specific regulatory domain is applied on affected hardware and persists across reboots?
Related: #9019. In my case, Wi-Fi appeared connected, but traffic was not passing.
View raw text
### System details Intel Macbook Pro 2017 (14,1), 16gb, omarchy 4.0.3-1 ### What's wrong? After a fresh Omarchy installation, Wi-Fi showed as connected to my local network, but connectivity did not work. Pings timed out with 100% packet loss, and I could not download system updates. Running the following restored connectivity: ```bash sudo iw reg set US ``` Expected behavior: Wi-Fi connectivity should work after installation without manually setting the regulatory domain. Could the installer ensure that the appropriate country-specific regulatory domain is applied on affected hardware and persists across reboots? Related: #9019. In my case, Wi-Fi appeared connected, but traffic was not passing.
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.