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.
System update overwrote resolv.conf on NetworkManager system and broke DNS
Reported by markjfisher · filed Oct 22, 2025Closed upstream on 2026-07-18 by dhh. GitHub close reason: completed. No closing PR or commit is recorded — "completed" alone is not 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
Omarchy 3.1.1
What's wrong?
I did a system update this morning, and it overwrote my NetworkManger managed /etc/resolv.d with a symlink to /run/systemd/resolve/stub-resolv.conf
I don't have systemd-resolved or systemd-networkd enabled, as I use NetworkManager, so this broke my network.
Can omarchy be updated to detect when NetworkManger is enabled (or that system-resolved is not enabled) and not amend files it controls?
For anyone this affects I had to:
> sudo rm /etc/resolv.conf
> sudo ln -s /run/NetworkManager/resolv.conf /etc/resolv.conf
> sudo systemctl restart NetworkManagerThen shortly after DNS started working again.
View raw text
### System details Omarchy 3.1.1 ### What's wrong? I did a system update this morning, and it overwrote my NetworkManger managed /etc/resolv.d with a symlink to /run/systemd/resolve/stub-resolv.conf I don't have systemd-resolved or systemd-networkd enabled, as I use NetworkManager, so this broke my network. Can omarchy be updated to detect when NetworkManger is enabled (or that system-resolved is not enabled) and not amend files it controls? For anyone this affects I had to: ```shell > sudo rm /etc/resolv.conf > sudo ln -s /run/NetworkManager/resolv.conf /etc/resolv.conf > sudo systemctl restart NetworkManager ``` Then shortly after DNS started working again.
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.
No decision has been recorded yet.