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.
Quattro upgrade leaves legacy wpa_supplicant mask in place; all wifi stuck unavailable
Reported by twagner12 · filed Aug 13, 2026Closed upstream on 2026-08-13 by the merge of PR #6793 (closed by dhh). 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
Omarchy 3.8.4 → Quattro, dev channel, upgraded 2026-08-12. Intel BE200 Wi-Fi 7 [8086:a840], iwlwifi, interface wlp0s20f3.
What's wrong?
After the upgrade and reboot, no wifi. nmcli device status shows both wifi and ethernet as unavailable. rfkill list shows nothing blocked, nmcli radio wifi reports enabled, and NetworkManager.service is active and running.
Logs:
device (wlp0s20f3): Couldn't initialize supplicant interface: Failed to D-Bus activate wpa_supplicant service
device (wlp0s20f3): re-acquiring supplicant interface (#2)
[repeats through #5]
device (wlp0s20f3): supplicant interface keeps failing, giving up
Cause: /etc/systemd/system/wpa_supplicant.service was masked — a legacy state from the iwd era, where wpa_supplicant was kept out of the way. Quattro removes iwd and points NetworkManager at wpa_supplicant, but doesn't check whether the unit is masked.
To be clear about attribution: grep -rn "systemctl mask" across the Omarchy checkout shows Omarchy only masks NetworkManager-wait-online.service and systemd-networkd-wait-online.service. It does not mask wpa_supplicant. So this affects installs carrying the mask from elsewhere — but iwd-era systems are a plausible population for that.
Fix:
sudo systemctl unmask wpa_supplicant
sudo systemctl enable --now wpa_supplicant
sudo systemctl restart NetworkManager
Device moved unavailable → disconnected immediately and connected normally.
Why it's worth handling in migration: the symptom is total loss of network, so the affected user can't research it from the machine it happened on.
Secondary, minor: once connected, the network panel shows the SSID with live ping/throughput/IP but the label underneath still reads "NOT CONNECTED."
View raw text
### System details Omarchy 3.8.4 → Quattro, dev channel, upgraded 2026-08-12. Intel BE200 Wi-Fi 7 [8086:a840], iwlwifi, interface wlp0s20f3. ### What's wrong? After the upgrade and reboot, no wifi. nmcli device status shows both wifi and ethernet as unavailable. rfkill list shows nothing blocked, nmcli radio wifi reports enabled, and NetworkManager.service is active and running. Logs: device (wlp0s20f3): Couldn't initialize supplicant interface: Failed to D-Bus activate wpa_supplicant service device (wlp0s20f3): re-acquiring supplicant interface (#2) [repeats through #5] device (wlp0s20f3): supplicant interface keeps failing, giving up Cause: /etc/systemd/system/wpa_supplicant.service was masked — a legacy state from the iwd era, where wpa_supplicant was kept out of the way. Quattro removes iwd and points NetworkManager at wpa_supplicant, but doesn't check whether the unit is masked. To be clear about attribution: grep -rn "systemctl mask" across the Omarchy checkout shows Omarchy only masks NetworkManager-wait-online.service and systemd-networkd-wait-online.service. It does not mask wpa_supplicant. So this affects installs carrying the mask from elsewhere — but iwd-era systems are a plausible population for that. Fix: sudo systemctl unmask wpa_supplicant sudo systemctl enable --now wpa_supplicant sudo systemctl restart NetworkManager Device moved unavailable → disconnected immediately and connected normally. Why it's worth handling in migration: the symptom is total loss of network, so the affected user can't research it from the machine it happened on. Secondary, minor: once connected, the network panel shows the SSID with live ping/throughput/IP but the label underneath still reads "NOT CONNECTED."
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.