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.
Wi-Fi panel is unreachable from Setup/Apps once the bar widget is removed
Reported by smfworks · filed Sep 8, 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?
- 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. So far: partly in the audited area (menu) — decided by agents · verified; matches no known issue — decided by agents · verified. The outcome (valid, duplicate, not a bug, …) is not decided yet. See the decision.
Original report
System details
Surface Laptop 4 Intel (i7-1185G7), Omarchy 4.0.2-1 (quattro), kernel 7.1.9-arch1-2
What's wrong?
NetworkManager itself is fine. The Omarchy Wi-Fi panel (omarchy.network) is only discoverable from the bar widget (and Super + Ctrl + W).
Setup > Network currently has DNS and QR Code, but no action that opens the scan/connect panel. There is also no .desktop launcher, so searching Apps for "Wi-Fi" / "Network Manager" finds nothing.
That matters as soon as the bar widget is gone — a slim custom shell.json, omarchy plugin disable omarchy.network, or dragging the widget off the bar. Travelers then have no menu or app path to switch SSIDs.
Steps
- Remove
omarchy.networkfrom the bar (omarchy plugin disable omarchy.network, or drop it from~/.config/omarchy/shell.json). - Open Setup > Network.
- Search the app launcher for Wi-Fi.
Expected
Setup > Network includes a Wi-Fi row that summons the same panel as the bar icon. Apps also has a Wi-Fi launcher. The hotkey still works.
Actual
Setup > Network is only DNS + QR. No app launcher. Only Super + Ctrl + W still opens the panel, which is easy to miss if you came looking for Network Manager.
Not asking to force the widget back onto a custom bar. Just a discoverable launch path that still works when the icon is gone.
View raw text
### System details Surface Laptop 4 Intel (i7-1185G7), Omarchy 4.0.2-1 (quattro), kernel 7.1.9-arch1-2 ### What's wrong? NetworkManager itself is fine. The Omarchy Wi-Fi panel (`omarchy.network`) is only discoverable from the bar widget (and `Super + Ctrl + W`). `Setup > Network` currently has DNS and QR Code, but no action that opens the scan/connect panel. There is also no `.desktop` launcher, so searching Apps for "Wi-Fi" / "Network Manager" finds nothing. That matters as soon as the bar widget is gone — a slim custom `shell.json`, `omarchy plugin disable omarchy.network`, or dragging the widget off the bar. Travelers then have no menu or app path to switch SSIDs. **Steps** 1. Remove `omarchy.network` from the bar (`omarchy plugin disable omarchy.network`, or drop it from `~/.config/omarchy/shell.json`). 2. Open Setup > Network. 3. Search the app launcher for Wi-Fi. **Expected** Setup > Network includes a Wi-Fi row that summons the same panel as the bar icon. Apps also has a Wi-Fi launcher. The hotkey still works. **Actual** Setup > Network is only DNS + QR. No app launcher. Only `Super + Ctrl + W` still opens the panel, which is easy to miss if you came looking for Network Manager. Not asking to force the widget back onto a custom bar. Just a discoverable launch path that still works when the icon is gone.
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
- Related PRpr/7763· confirmed
- Fixed bypr/10805· confirmed
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.
- Decided by agents · verified: partly in the audited area (menu)
- Decided by agents · verified: matches no known issue
The outcome (valid, duplicate, not a bug, …) is not decided yet.