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-speedtest: orphaned processes run indefinitely when Quickshell restarts
Reported by seba-rb · filed Aug 27, 2026Closed upstream on 2026-10-05 by its own reporter seba-rb. GitHub close reason: completed. Closed by its own reporter — not by itself evidence of a fix.
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
System details
Intel Core (4 cores), Omarchy 4.0.1-1, kernel 7.1.9-arch1-2
What's wrong?
What's wrong
When Quickshell restarts or crashes while the speedtest panel is open, the omarchy-network-speedtest child processes become orphaned (re-parented to systemd) and run forever. The cleanup() trap in the script only fires on EXIT, which never happens if the parent process dies without sending SIGTERM.
Each restart leaves another set of instances behind. I found 7 orphaned instances all in up mode, each with 8 parallel curl workers saturating the link — totalling ~56 concurrent upload streams to Netflix OCA servers.
Observable symptoms
- Both fans at >7300 RPM (above the reported 7000 RPM max, PWM at 128%)
- Wi-Fi card at 76°C
ps auxshows multipleomarchy-network-speedtest upprocesses withsystemd --useras parent (PID 1)
sebarb 1159822 ... /bin/bash /usr/share/omarchy/bin/omarchy-network-speedtest up
sebarb 1159823 ... /bin/bash /usr/share/omarchy/bin/omarchy-network-speedtest up
sebarb 1159824 ... /bin/bash /usr/share/omarchy/bin/omarchy-network-speedtest up
... (7 total)Root cause
Process {} elements in QML do not guarantee SIGTERM delivery to children when Quickshell itself is killed with SIGKILL or crashes. The bash script's trap cleanup EXIT is therefore never triggered, and the while true loop inside traffic_worker() runs indefinitely.
Suggested fix
Add a parent-death guard at the top of omarchy-network-speedtest, before spawning workers:
# Die when our parent dies
( while kill -0 $PPID 2>/dev/null; do sleep 1; done; kill -- -$$ 2>/dev/null ) &This polls the parent PID and sends SIGTERM to the script's process group when the parent is gone, which triggers cleanup() and terminates the curl workers cleanly.
Alternatively, use a lock file or a named pipe whose read end is held by the QML Process — closing the process would close the pipe, and the script could detect EOF and exit.
Steps to reproduce
- Open the speedtest panel
- Kill or restart Quickshell (
killall -9 qs) while the test is running - Check
ps aux | grep omarchy-network-speedtest— processes remain running indefinitely
View raw text
### System details
Intel Core (4 cores), Omarchy 4.0.1-1, kernel 7.1.9-arch1-2
### What's wrong?
## What's wrong
When Quickshell restarts or crashes while the speedtest panel is open, the `omarchy-network-speedtest` child processes become orphaned (re-parented to systemd) and **run forever**. The `cleanup()` trap in the script only fires on `EXIT`, which never happens if the parent process dies without sending `SIGTERM`.
Each restart leaves another set of instances behind. I found **7 orphaned instances** all in `up` mode, each with 8 parallel `curl` workers saturating the link — totalling ~56 concurrent upload streams to Netflix OCA servers.
## Observable symptoms
- Both fans at >7300 RPM (above the reported 7000 RPM max, PWM at 128%)
- Wi-Fi card at 76°C
- `ps aux` shows multiple `omarchy-network-speedtest up` processes with `systemd --user` as parent (PID 1)
```
sebarb 1159822 ... /bin/bash /usr/share/omarchy/bin/omarchy-network-speedtest up
sebarb 1159823 ... /bin/bash /usr/share/omarchy/bin/omarchy-network-speedtest up
sebarb 1159824 ... /bin/bash /usr/share/omarchy/bin/omarchy-network-speedtest up
... (7 total)
```
## Root cause
`Process {}` elements in QML do not guarantee `SIGTERM` delivery to children when Quickshell itself is killed with `SIGKILL` or crashes. The bash script's `trap cleanup EXIT` is therefore never triggered, and the `while true` loop inside `traffic_worker()` runs indefinitely.
## Suggested fix
Add a parent-death guard at the top of `omarchy-network-speedtest`, before spawning workers:
```bash
# Die when our parent dies
( while kill -0 $PPID 2>/dev/null; do sleep 1; done; kill -- -$$ 2>/dev/null ) &
```
This polls the parent PID and sends `SIGTERM` to the script's process group when the parent is gone, which triggers `cleanup()` and terminates the curl workers cleanly.
Alternatively, use a lock file or a named pipe whose read end is held by the QML `Process` — closing the process would close the pipe, and the script could detect EOF and exit.
## Steps to reproduce
1. Open the speedtest panel
2. Kill or restart Quickshell (`killall -9 qs`) while the test is running
3. Check `ps aux | grep omarchy-network-speedtest` — processes remain running indefinitelyValidation
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.