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 panel header says "No connection" while the list below shows the connected network
Reported by travelingnomad1 · filed Oct 7, 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
Opening the network panel while fully connected shows a contradiction: the
header reads "No connection", while the KNOWN NETWORKS list immediately
below correctly shows the active SSID marked "Connected".
The machine is genuinely online at that moment — nmcli reportsconnected / full, the interface has an address and gateway, and both DNS
and an HTTP connectivity check succeed.
Expected
The header should show the connected SSID, or show nothing / "Connecting…"
until it has data — but it should not assert "No connection" while connected.
Cause
The two halves of the panel are fed from different sources with different
latencies:
- the network list is populated promptly;
- the header reads
root.info, which is filled bydetailsProc
(Panel.qml:812, command: ["omarchy-network-status", "--verbose"]).
Until that first result arrives, root.info is still {}, soroot.info.type is undefined and the title falls through to the default atPanel.qml:1180:
return root.info.iface || (root.kind === "disconnected" ? "Disconnected" : "No connection")omarchy-network-status --verbose is not instant — it shells out several
times and pings both the router and the internet (it reportsrouter_ping_ms and internet_ping_ms). Measured on this machine it takes
~100 ms when the link is healthy, but it is bounded by those pings, so on a
slow or lossy link it takes considerably longer, which is when the wrong
header is visible long enough to notice. The source's own comment calls this
the deliberately slower poll.
Suggested fix
Distinguish "no data yet" from "disconnected" — e.g. keep the header blank or
show a connecting state until detailsProc has returned once, or seed the
header from the same source the network list uses.
Steps to reproduce
- Connect to Wi-Fi.
- Open the network panel (ideally on a link with high ping, which widens the
window).
3. Observe the header reads "No connection" while the list shows the SSID as
Connected.
System
- Omarchy 4.0.4-1, omarchy-settings 4.0.4-1
- Quickshell 0.3.1-1
- Kernel 7.2.5-3-omarchy
- CPU Intel Core i7-7Y75 / GPU Intel HD Graphics 615 (Kaby Lake-Y)
- Google Pixelbook (Eve)
Evidence
Screenshot attached (header "No connection" above list entry "Connected").
View raw text
### What happened
Opening the network panel while fully connected shows a contradiction: the
header reads **"No connection"**, while the KNOWN NETWORKS list immediately
below correctly shows the active SSID marked **"Connected"**.
The machine is genuinely online at that moment — `nmcli` reports
`connected / full`, the interface has an address and gateway, and both DNS
and an HTTP connectivity check succeed.
### Expected
The header should show the connected SSID, or show nothing / "Connecting…"
until it has data — but it should not assert "No connection" while connected.
### Cause
The two halves of the panel are fed from different sources with different
latencies:
- the network list is populated promptly;
- the header reads `root.info`, which is filled by `detailsProc`
(`Panel.qml:812`, `command: ["omarchy-network-status", "--verbose"]`).
Until that first result arrives, `root.info` is still `{}`, so
`root.info.type` is undefined and the title falls through to the default at
`Panel.qml:1180`:
```qml
return root.info.iface || (root.kind === "disconnected" ? "Disconnected" : "No connection")
```
`omarchy-network-status --verbose` is not instant — it shells out several
times and pings both the router and the internet (it reports
`router_ping_ms` and `internet_ping_ms`). Measured on this machine it takes
~100 ms when the link is healthy, but it is bounded by those pings, so on a
slow or lossy link it takes considerably longer, which is when the wrong
header is visible long enough to notice. The source's own comment calls this
the deliberately slower poll.
### Suggested fix
Distinguish "no data yet" from "disconnected" — e.g. keep the header blank or
show a connecting state until `detailsProc` has returned once, or seed the
header from the same source the network list uses.
### Steps to reproduce
1. Connect to Wi-Fi.
2. Open the network panel (ideally on a link with high ping, which widens the
window).
3. Observe the header reads "No connection" while the list shows the SSID as
Connected.
### System
- Omarchy 4.0.4-1, omarchy-settings 4.0.4-1
- Quickshell 0.3.1-1
- Kernel 7.2.5-3-omarchy
- CPU Intel Core i7-7Y75 / GPU Intel HD Graphics 615 (Kaby Lake-Y)
- Google Pixelbook (Eve)
### Evidence
Screenshot attached (header "No connection" above list entry "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.
- Out of scopeDecided by agents · verified · 2026-10-09 22:02 UTC