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.
NordVPN installation appears to report a successful installation even when the installation is interrupted and the requires sudo authentication fails
Reported by RajivAnandKhanal · filed Aug 23, 2026Closed upstream on 2026-09-29 by its own reporter RajivAnandKhanal. 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
i5 11 gen, 12 gigs ram
What's wrong?
If NordVPN is not installed then in the menu (windows + space), it shows the option to install directly from menu. When you choose to install via menu instead of package installer option, then terminal opens for installation, But if installation is cancelled instead of providing sudo password, it still continues even after saying sudo password is required.
This requires Nordvpn not to installed already
Steps to reproduce
- Open the menu (windows + space). Type Nord, and choose to install
- Start the installation.
- When prompted for the sudo password, press
Ctrl+Cinstead of entering the password. - Observe the installer output.
Actual behavior
The installer continues executing subsequent steps even though sudo commands fail:
Installing NordVPN...
[sudo] password for omarchy:
sudo: a password is required
Enabling NordVPN daemon...
[sudo] password for omarchy:
sudo: a password is required
Adding user to nordvpn group...
[sudo] password for omarchy:
sudo: a password is required
It then reports:
NordVPN installed! After reboot, run 'nordvpn login' to authenticate.
However, the installation was not completed successfully.
In my case, systemd also ended up with active NordVPN-related units while their unit files were missing, resulting in:
Loaded: not-found (Reason: Unit nordvpnd.service not found.)
Active: active (running)
For example, a dangling symlink was present:
/etc/systemd/system/default.target.wants/nordvpnd.service
-> /usr/lib/systemd/system/nordvpnd.service
but /usr/lib/systemd/system/nordvpnd.service did not exist.
Expected behavior
If the installation is interrupted or a required sudo command fails, the installer should:
- Stop the installation.
- Report that the installation failed/interrupted.
- Avoid reporting "NordVPN installed!".
- Ideally clean up any systemd units/symlinks that were created before the failure.
I can provide the relevant command output and logs if needed.
System details
- OS: Omarchy
- Linux omarchy 7.1.8-arch1-3 #1 SMP PREEMPT_DYNAMIC Tue, 11 Aug 2026 09:16:08 +0000 x86_64 GNU/Linux
- omarchy-version: 4.0.0-1
<img width="758" height="547" alt="Image" src="https://github.com/user-attachments/assets/c869c58a-d689-4bf4-8d75-773292c96afa" />
View raw text
### System details
i5 11 gen, 12 gigs ram
### What's wrong?
If NordVPN is not installed then in the menu (windows + space), it shows the option to install directly from menu. When you choose to install via menu instead of package installer option, then terminal opens for installation, But if installation is cancelled instead of providing sudo password, it still continues even after saying sudo password is required.
## This requires Nordvpn not to installed already
## Steps to reproduce
1. Open the menu (windows + space). Type Nord, and choose to install
2. Start the installation.
4. When prompted for the sudo password, press `Ctrl+C` instead of entering the password.
5. Observe the installer output.
## Actual behavior
The installer continues executing subsequent steps even though sudo commands fail:
Installing NordVPN...
[sudo] password for omarchy:
sudo: a password is required
Enabling NordVPN daemon...
[sudo] password for omarchy:
sudo: a password is required
Adding user to nordvpn group...
[sudo] password for omarchy:
sudo: a password is required
It then reports:
NordVPN installed! After reboot, run 'nordvpn login' to authenticate.
However, the installation was not completed successfully.
In my case, systemd also ended up with active NordVPN-related units while their unit files were missing, resulting in:
Loaded: not-found (Reason: Unit nordvpnd.service not found.)
Active: active (running)
For example, a dangling symlink was present:
/etc/systemd/system/default.target.wants/nordvpnd.service
-> /usr/lib/systemd/system/nordvpnd.service
but `/usr/lib/systemd/system/nordvpnd.service` did not exist.
## Expected behavior
If the installation is interrupted or a required sudo command fails, the installer should:
- Stop the installation.
- Report that the installation failed/interrupted.
- Avoid reporting "NordVPN installed!".
- Ideally clean up any systemd units/symlinks that were created before the failure.
## I can provide the relevant command output and logs if needed.
## System details
- OS: Omarchy
- Linux omarchy 7.1.8-arch1-3 #1 SMP PREEMPT_DYNAMIC Tue, 11 Aug 2026 09:16:08 +0000 x86_64 GNU/Linux
- omarchy-version: 4.0.0-1
<img width="758" height="547" alt="Image" src="https://github.com/user-attachments/assets/c869c58a-d689-4bf4-8d75-773292c96afa" />- c869c58a-d689-4bf4-8d75-773292c96afa
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.