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 speed test leaves orphaned workers uploading forever
Reported by pandey-adarsh147 · filed Oct 2, 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
System details: Intel i7-7700, Intel HD Graphics 630, Omarchy 4.0.4
What's wrong?
omarchy-network-speedtest can leave its traffic workers running forever after the script itself is gone. They are reparented to systemd --user and keep POSTing 64 MB blobs of zeros (upload) or downloading (download) against the fast.com / Netflix OCA endpoints until logout.
On my machine this went unnoticed for days: the wired interface showed ~196 GB uploaded since boot, and the router attributed the traffic to "Netflix". Per-process monitoring (picosnitch) caught a fresh set of orphans uploading 5.25 GB in ~3 minutes (~240 Mbit/s):
PID PPID COMMAND
1113128 898 /bin/bash /usr/share/omarchy/bin/omarchy-network-speedtest up # 898 = systemd --user
1113133 898 /bin/bash /usr/share/omarchy/bin/omarchy-network-speedtest up
...
curl -fsS -o /dev/null -X POST --data-binary @- https://ipv4-c029-maa001-ix.1.oca.nflxvideo.net/speedtest?...Cause
The workers are while true loops that are only stopped by the cleanup EXIT trap. A graceful SIGTERM runs the trap and everything stops correctly, but if the script is killed hard (SIGKILL, or killed partway through cleanup), the trap never completes and the remaining workers are orphaned with nothing left to stop them.
Steps to reproduce (offline)
With a stub curl on PATH that returns fake targets for the API call and just sleeps for transfers:
setsid omarchy-network-speedtest up &kill -KILL <script pid>pgrep -f omarchy-network-speedtest→ all 8 workers are still running, parented tosystemd --user, and never exit.
Same for down.
Expected
Workers stop once the script is gone, however it was terminated.
View raw text
**System details:** Intel i7-7700, Intel HD Graphics 630, Omarchy 4.0.4 ### What's wrong? `omarchy-network-speedtest` can leave its traffic workers running forever after the script itself is gone. They are reparented to `systemd --user` and keep POSTing 64 MB blobs of zeros (upload) or downloading (download) against the fast.com / Netflix OCA endpoints until logout. On my machine this went unnoticed for days: the wired interface showed **~196 GB uploaded** since boot, and the router attributed the traffic to "Netflix". Per-process monitoring (picosnitch) caught a fresh set of orphans uploading **5.25 GB in ~3 minutes** (~240 Mbit/s): ``` PID PPID COMMAND 1113128 898 /bin/bash /usr/share/omarchy/bin/omarchy-network-speedtest up # 898 = systemd --user 1113133 898 /bin/bash /usr/share/omarchy/bin/omarchy-network-speedtest up ... curl -fsS -o /dev/null -X POST --data-binary @- https://ipv4-c029-maa001-ix.1.oca.nflxvideo.net/speedtest?... ``` ### Cause The workers are `while true` loops that are only stopped by the `cleanup` EXIT trap. A graceful SIGTERM runs the trap and everything stops correctly, but if the script is killed hard (SIGKILL, or killed partway through `cleanup`), the trap never completes and the remaining workers are orphaned with nothing left to stop them. ### Steps to reproduce (offline) With a stub `curl` on `PATH` that returns fake targets for the API call and just sleeps for transfers: 1. `setsid omarchy-network-speedtest up &` 2. `kill -KILL <script pid>` 3. `pgrep -f omarchy-network-speedtest` → all 8 workers are still running, parented to `systemd --user`, and never exit. Same for `down`. ### Expected Workers stop once the script is gone, however it was terminated.
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 20:36 UTC