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.
Network bar and popup show disconnected while Wi-Fi is connected
Reported by numanzahid · filed Sep 10, 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
What happened\n\nThe Omarchy top-bar network icon shows Wi-Fi as disconnected. Clicking it opens the network panel, which also says disconnected.\n\n### What is expected\n\nThe icon and network panel should show the active Wi-Fi connection and signal strength.\n\n### What actually happened\n\nThe system is connected and has working connectivity, but the Omarchy UI reports disconnected.\n\nHost checks at the time of the issue:\n\n- NetworkManager reported the Wi-Fi device as connected\n- An active Wi-Fi connection was present\n- An IPv4 address and default route were present\n- Router ping: 3.57 ms\n- Internet ping: 6.72 ms\n- iface wlp108s0
ip 172.16.2.102
prefix 24
gateway 172.16.2.1
rx_bytes 396669961
tx_bytes 238363976
type wifi
ssid VoiceCrown
signal_dbm -55
freq 2437.0
bitrate 57.8 MBit/s
router_ping_ms 1.16
internet_ping_ms 3.74 reported Wi-Fi type, signal, and traffic counters\n\nThe bar and popup appear to share the Quickshell network backend, so both UI surfaces show the same incorrect state.\n\n### Steps to reproduce\n\n1. Connect to Wi-Fi.\n2. Confirm connectivity works.\n3. Observe the top-bar network icon.\n4. Click the network icon.\n5. Observe that the panel reports disconnected.\n\n### System details\n\n- Omarchy: 4.0.3-1\n- quickshell: 0.3.1-1\n- networkmanager: 1.58.1-1\n\nNo Wi-Fi name, IP address, user name, or other session-specific identifiers are included.\n\nThis may be a stale or failed Quickshell.Networking/NetworkManager state refresh.
View raw text
### What happened\n\nThe Omarchy top-bar network icon shows Wi-Fi as disconnected. Clicking it opens the network panel, which also says disconnected.\n\n### What is expected\n\nThe icon and network panel should show the active Wi-Fi connection and signal strength.\n\n### What actually happened\n\nThe system is connected and has working connectivity, but the Omarchy UI reports disconnected.\n\nHost checks at the time of the issue:\n\n- NetworkManager reported the Wi-Fi device as connected\n- An active Wi-Fi connection was present\n- An IPv4 address and default route were present\n- Router ping: 3.57 ms\n- Internet ping: 6.72 ms\n- iface wlp108s0 ip 172.16.2.102 prefix 24 gateway 172.16.2.1 rx_bytes 396669961 tx_bytes 238363976 type wifi ssid VoiceCrown signal_dbm -55 freq 2437.0 bitrate 57.8 MBit/s router_ping_ms 1.16 internet_ping_ms 3.74 reported Wi-Fi type, signal, and traffic counters\n\nThe bar and popup appear to share the Quickshell network backend, so both UI surfaces show the same incorrect state.\n\n### Steps to reproduce\n\n1. Connect to Wi-Fi.\n2. Confirm connectivity works.\n3. Observe the top-bar network icon.\n4. Click the network icon.\n5. Observe that the panel reports disconnected.\n\n### System details\n\n- Omarchy: 4.0.3-1\n- quickshell: 0.3.1-1\n- networkmanager: 1.58.1-1\n\nNo Wi-Fi name, IP address, user name, or other session-specific identifiers are included.\n\nThis may be a stale or failed Quickshell.Networking/NetworkManager state refresh.
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 11:31 UTC