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.
Use NetworkManager instead of systemd-networkd
Reported by kromsam · filed Sep 2, 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
Is closed by merging: https://github.com/basecamp/omarchy/pull/2909
NetworkManager has become the de facto standard in the Linux Desktop space. Whereas systemd-networkd is very minimal, and good enough for set-and-forget networking on a server, it has it's limitations when it comes to desktop and laptop usage. Where we often switch networks, and rely on extra functionality (such as VPNs and Enterprise Networks) to work without a lot of custom configuration.
I have really like Omarchy so far, but I think systemd-networkd is not a viable option for a complete desktop system. Especially when trying to set up my VPN or when I try to use Enterprise Networks such as eduroam and 802.1.x/owe.
NetworkManager 'just works'! It's the default option for all the major desktop environments (GNOME / KDE / Cinnamon) and Linux distros (like Omakub). Many desktop applications for networking, such as VPN clients rely on it.
So, on behalf of all people that try to:
- set up a VPN through a GUI (like ProtonVPN, or EduVPN)
- connect to eduroam through the CLI
- connect to a modern WiFI standard like 'Enhanced Open'
Can we please just use NetworkManager?
edit: have been trying to connect to a new network in a flex work space for an hour and im almost capable of throwing my laptop through the space out of frustration
edit: still no luck, i give up and go home. apparently systemd-networkd cannot handle the 'Enhanced Open' wifi standard. awful experience!
And as long as Omarchy hasn't switched...
You can still do it yourself! It's very easy. Now with Gazelle there is a proper TUI alternative for Impala (which is what initially kept us from using NetworkManager).
In the comments below I have written a step-by-step guide of making the switch yourself: https://github.com/basecamp/omarchy/issues/1414#issuecomment-4811643281
I have written a PR that makes minimal changes to the system necessary for switching over: #2909. This PR also takes care of changing other networking script such as DNS-switching, and it will integrate Gazelle into your system. You can also use this as a source if you want to make the switch, I will keep this PR up to date.
View raw text
Is closed by merging: https://github.com/basecamp/omarchy/pull/2909 NetworkManager has become the _de facto_ standard in the Linux Desktop space. Whereas systemd-networkd is very minimal, and good enough for set-and-forget networking on a server, it has it's limitations when it comes to desktop and laptop usage. Where we often switch networks, and rely on extra functionality (such as VPNs and Enterprise Networks) to work without a lot of custom configuration. I have really like Omarchy so far, but I think systemd-networkd is not a viable option for a complete desktop system. Especially when trying to set up my VPN or when I try to use Enterprise Networks such as eduroam and 802.1.x/owe. NetworkManager 'just works'! It's the default option for all the major desktop environments (GNOME / KDE / Cinnamon) and Linux distros (like Omakub). Many desktop applications for networking, such as VPN clients rely on it. So, on behalf of all people that try to: - set up a VPN through a GUI (like ProtonVPN, or EduVPN) - connect to eduroam through the CLI - connect to a modern WiFI standard like 'Enhanced Open' Can we please just use NetworkManager? edit: have been trying to connect to a new network in a flex work space for an hour and im almost capable of throwing my laptop through the space out of frustration edit: still no luck, i give up and go home. apparently systemd-networkd cannot handle the 'Enhanced Open' wifi standard. awful experience! ## And as long as Omarchy hasn't switched... You can still do it yourself! It's very easy. Now with Gazelle there is a proper TUI alternative for Impala (which is what initially kept us from using NetworkManager). In the comments below I have written a step-by-step guide of making the switch yourself: https://github.com/basecamp/omarchy/issues/1414#issuecomment-4811643281 I have written a PR that makes minimal changes to the system necessary for switching over: #2909. This PR also takes care of changing other networking script such as DNS-switching, and it will integrate Gazelle into your system. You can also use this as a source if you want to make the switch, I will keep this PR up to date.
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.