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.
omarchy-network-status: 100% packet loss when 1.1.1.1 is unreachable
Reported by 0zgenius · filed Aug 30, 2026Closed upstream on 2026-09-21 by bjarneo via an automated message, as a duplicate of #9068 (R-1232). 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
Description
omarchy-network-status hardcodes 1.1.1.1 (Cloudflare DNS) as the sole internet ping probe. On networks that block ICMP to 1.1.1.1, the network panel shows "Timeout" and "100% Packet Loss" — even though the internet connection is fully functional and data is flowing normally.
Steps to Reproduce
- Connect to a network that blocks ICMP to
1.1.1.1(but allows it to other hosts like8.8.8.8) - Open the network panel
- Observe "Timeout" / "100% Packet Loss" despite working internet
Expected Behavior
Panel shows real latency and 0% packet loss.
Actual Behavior
Panel shows Timeout / 100% loss.
Suggested Fix
Try multiple probe addresses (1.1.1.1, 8.8.8.8, 9.9.9.9, 208.67.222.222) and use the first that responds. I've locally patched omarchy-network-status with this approach and it works correctly:
ping_best_internet_probe() {
local result
result=$(ping_latency_ms "$internet_probe")
if [[ -n $result ]]; then
printf '%s' "$result"
return
fi
local probe
for probe in $internet_fallback_probes; do
result=$(ping_latency_ms "$probe")
if [[ -n $result ]]; then
printf '%s' "$result"
return
fi
done
}Environment
- Omarchy latest
- Network:
ozgenius_5G(5GHz Wi-Fi) - Router/gateway reachable, internet functional, but
1.1.1.1ICMP blocked
View raw text
## Description
`omarchy-network-status` hardcodes `1.1.1.1` (Cloudflare DNS) as the sole internet ping probe. On networks that block ICMP to `1.1.1.1`, the network panel shows "Timeout" and "100% Packet Loss" — even though the internet connection is fully functional and data is flowing normally.
## Steps to Reproduce
1. Connect to a network that blocks ICMP to `1.1.1.1` (but allows it to other hosts like `8.8.8.8`)
2. Open the network panel
3. Observe "Timeout" / "100% Packet Loss" despite working internet
## Expected Behavior
Panel shows real latency and 0% packet loss.
## Actual Behavior
Panel shows Timeout / 100% loss.
## Suggested Fix
Try multiple probe addresses (`1.1.1.1`, `8.8.8.8`, `9.9.9.9`, `208.67.222.222`) and use the first that responds. I've locally patched `omarchy-network-status` with this approach and it works correctly:
```bash
ping_best_internet_probe() {
local result
result=$(ping_latency_ms "$internet_probe")
if [[ -n $result ]]; then
printf '%s' "$result"
return
fi
local probe
for probe in $internet_fallback_probes; do
result=$(ping_latency_ms "$probe")
if [[ -n $result ]]; then
printf '%s' "$result"
return
fi
done
}
```
## Environment
- Omarchy latest
- Network: `ozgenius_5G` (5GHz Wi-Fi)
- Router/gateway reachable, internet functional, but `1.1.1.1` ICMP blockedValidation
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.