Proof Portal

Sign in
Project overview

Omarchy

ProbeLabs65 findings · 95 requirements

A 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.

Inbox
ReportR-2009GitHub issuePublicDecided· Out of scope

Ctrl+C during sudo password prompt in pkg-install/pkg-aur-install does not abort the process

Reported by Bartmax · filed Mar 2, 2026 · open at source

Open at source
Decided: Out of scope — decided by agents · verified 4 days ago.

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?
AreaOutside the audited area· Decided by agents · verified
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?
Decided by agents and verified by a second, independent agent — see the decision.

Original report

Ctrl+C during sudo password prompt in pkg-install/pkg-aur-install does not abort the processrevision 1 · captured 2026-09-28 21:29 UTC via poll

System details

Omarchy 3.4.1

What's wrong?

When omarchy-pkg-install or omarchy-pkg-aur-install prompts for a sudo password and the user presses Ctrl+C to cancel, the scripts continue executing as if nothing was
aborted — including showing the "done" notification and (in the AUR case) running sudo updatedb.

Root cause

Neither script uses set -e or chains commands with &&/|| exit, so a failed/interrupted command doesn't stop execution.

In omarchy-pkg-install:

echo "$pkg_names" | tr '\n' ' ' | xargs sudo pacman -S --noconfirm
omarchy-show-done  # runs even if the above was aborted

In omarchy-pkg-aur-install:

sudo -v            # Ctrl+C here kills sudo-v but...
echo "$pkg_names" | sed 's/^/aur\//' | tr '\n' ' ' | xargs yay -S --noconfirm  
# ...this still runs
sudo updatedb
omarchy-show-done

Proposed fix

Chain commands so failure/abort stops execution:

omarchy-pkg-install:
echo "$pkg_names" | tr '\n' ' ' | xargs sudo pacman -S --noconfirm && omarchy-show-done
omarchy-pkg-aur-install:
sudo -v || exit 1
echo "$pkg_names" | sed 's/^/aur\//' | tr '\n' ' ' | xargs yay -S --noconfirm || exit 1
sudo updatedb
omarchy-show-done

Happy to open a PR with this fix if welcome.

View raw text
### System details

Omarchy 3.4.1

### What's wrong?

When omarchy-pkg-install or omarchy-pkg-aur-install prompts for a sudo password and the user presses Ctrl+C to cancel, the scripts continue executing as if nothing was
  aborted — including showing the "done" notification and (in the AUR case) running sudo updatedb.

  Root cause

  Neither script uses set -e or chains commands with &&/|| exit, so a failed/interrupted command doesn't stop execution.

  In omarchy-pkg-install:
```` 
echo "$pkg_names" | tr '\n' ' ' | xargs sudo pacman -S --noconfirm
omarchy-show-done  # runs even if the above was aborted
````
  In omarchy-pkg-aur-install:
````
sudo -v            # Ctrl+C here kills sudo-v but...
echo "$pkg_names" | sed 's/^/aur\//' | tr '\n' ' ' | xargs yay -S --noconfirm  
# ...this still runs
sudo updatedb
omarchy-show-done
````
  Proposed fix

  Chain commands so failure/abort stops execution:
````
omarchy-pkg-install:
echo "$pkg_names" | tr '\n' ' ' | xargs sudo pacman -S --noconfirm && omarchy-show-done
````

````
omarchy-pkg-aur-install:
sudo -v || exit 1
echo "$pkg_names" | sed 's/^/aur\//' | tr '\n' ' ' | xargs yay -S --noconfirm || exit 1
sudo updatedb
omarchy-show-done
```` 
  Happy to open a PR with this fix if welcome.

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.

  • Out of scopeDecided by agents · verified · 2026-10-09 02:38 UTC