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 failure due to NetworkManager removal and r8168/r8169 driver conflict
Reported by n4zguu1 · filed Apr 20, 2026Closed upstream on 2026-04-20 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
RTX 3060TI, AMD R5 5600G
What's wrong?
After applying the latest system update, ethernet connectivity is lost. The update logic uninstalls NetworkManager in favor of systemd-networkd and installs the r8168 package, which blacklists the native r8169 driver.
View raw text
### System details RTX 3060TI, AMD R5 5600G ### What's wrong? After applying the latest system update, ethernet connectivity is lost. The update logic uninstalls NetworkManager in favor of systemd-networkd and installs the r8168 package, which blacklists the native r8169 driver.
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.