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.
No networking until after local login
Reported by warnockf · filed Dec 29, 2025Closed upstream on 2025-12-30 by its own reporter warnockf. 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
Omarchy 3.2.3, Realtek RTL8125
What's wrong?
The network daemon doesn't appear to initialize until after you log in to a local session, breaking the ability to run the system remotely. I have tried with my system's 2.5GB PCIe card as well as the onboard gigabit ethernet controller (also Realtek), both are wired connections and do not have any custom configuration.
How to reproduce
This can be reproduced by rebooting the system via sudo reboot and then observing that you can't even ping the machine once it comes back online.
Looking at journalctl -u systemd-networkd -b after letting the machine sit at the login screen for a few minutes, I can see that the log messages regarding bringing the interfaces up have timestamps that begin after I finally log in locally.
Workaround
Logging in via the lock screen appears to initialize the network daemon.
View raw text
### System details Omarchy 3.2.3, Realtek RTL8125 ### What's wrong? The network daemon doesn't appear to initialize until after you log in to a local session, breaking the ability to run the system remotely. I have tried with my system's 2.5GB PCIe card as well as the onboard gigabit ethernet controller (also Realtek), both are wired connections and do not have any custom configuration. #### How to reproduce This can be reproduced by rebooting the system via `sudo reboot` and then observing that you can't even ping the machine once it comes back online. Looking at `journalctl -u systemd-networkd -b` after letting the machine sit at the login screen for a few minutes, I can see that the log messages regarding bringing the interfaces up have timestamps that begin after I finally log in locally. #### Workaround Logging in via the lock screen appears to initialize the network daemon.
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.