Proof Portal

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-3611GitHub issuePublicFixed

Fix: Replace hardcoded 'yay' with 'paru' (or other) in Omarchy scripts to avoid AUR menu breakage

Reported by zestfulmouse · filed Nov 1, 2025Closed upstream on 2025-11-03 by dhh. GitHub close reason: completed. No closing PR or commit is recorded — "completed" alone is not evidence of a fix.

Received and recorded verbatim. Nothing has been checked yet.

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

Fix: Replace hardcoded 'yay' with 'paru' (or other) in Omarchy scripts to avoid AUR menu breakagerevision 1 · captured 2026-10-04 11:42 UTC via poll

What correction or addition do we need?

Problem:

Omarchy’s scripts hardcode the yay AUR helper, causing AUR packages to disappear from menus (e.g., omarchy-menu, omarchy-pkg-install) when users switch to paru or another helper. This breaks the user experience.

Root Cause:
Only scripts in /home/$USER/.local/share/omarchy/bin/ use yay directly. Other matches are false positives (binaries/comments).

Solution:
Replace all occurrences of yay with paru (or any other AUR helper) in the following scripts:
- omarchy-menu
- omarchy-pkg-aur-install
- omarchy-pkg-install
- omarchy-pkg-remove

Steps to Fix:
1. Replace `yay` with `paru` (or the name of your helper) in each script:

   sudo sed -i 's/yay/paru/g' /home/$USER/.local/share/omarchy/bin/omarchy-menu 
   sudo sed -i 's/yay/paru/g' /home/$USER/.local/share/omarchy/bin/omarchy-pkg-aur-install
   sudo sed -i 's/yay/paru/g' /home/$USER/.local/share/omarchy/bin/omarchy-pkg-install
   sudo sed -i 's/yay/paru/g' /home/$USER/.local/share/omarchy/bin/omarchy-pkg-remove
   sudo sed -i 's/yay/paru/g' /home/$USER/.local/share/omarchy/bin/omarchy-update-system-pkgs
  1. Verify changes:
   grep -r "paru" /home/$USER/.local/share/omarchy/bin/  # Confirm replacements
  1. Ensure executability:
   sudo chmod +x /home/$USER/.local/share/omarchy/bin/*
  1. Test:
   /home/$USER/.local/share/omarchy/bin/omarchy-menu  # Should now work with paru

Or super+alt+space and Install → AUR or Remove → Package

Notes:
- Tested on Omarchy vX.X: AUR packages reappear in menus after this change.
- paru supports all yay flags (e.g., --noconfirm).
- No false positives in other system files.

Proposed PR:
I can submit a PR with:
- A script to automate the replacement (e.g., omarchy-switch-helper).
- Direct patches to the 4 scripts above.
- Updated documentation in docs/aur-helper.md.

Question for Maintainers:
- Should the helper name be a variable (e.g., $AUR_HELPER) for future flexibility?
- Preferred location for a helper-switching script (if needed)?

I’m still learning Git/GitHub and bash, so if my issue or future PR needs adjustments, just let me know—I’m happy to improve!

View raw text
### What correction or addition do we need?

### **Problem**:
Omarchy’s scripts hardcode the `yay` AUR helper, causing AUR packages to disappear from menus (e.g., `omarchy-menu`, `omarchy-pkg-install`) when users switch to `paru` or another helper. This breaks the user experience.

**Root Cause**:
Only scripts in `/home/$USER/.local/share/omarchy/bin/` use `yay` directly. Other matches are false positives (binaries/comments).

**Solution**:
Replace all occurrences of `yay` with `paru` (or any other AUR helper) in the following scripts:
- `omarchy-menu`
- `omarchy-pkg-aur-install`
- `omarchy-pkg-install`
- `omarchy-pkg-remove`

**Steps to Fix**:
1. **Replace `yay` with `paru`** (or the name of your helper) in each script:
   ```bash
   sudo sed -i 's/yay/paru/g' /home/$USER/.local/share/omarchy/bin/omarchy-menu 
   sudo sed -i 's/yay/paru/g' /home/$USER/.local/share/omarchy/bin/omarchy-pkg-aur-install
   sudo sed -i 's/yay/paru/g' /home/$USER/.local/share/omarchy/bin/omarchy-pkg-install
   sudo sed -i 's/yay/paru/g' /home/$USER/.local/share/omarchy/bin/omarchy-pkg-remove
   sudo sed -i 's/yay/paru/g' /home/$USER/.local/share/omarchy/bin/omarchy-update-system-pkgs
   ```
2. **Verify changes**:
   ```bash
   grep -r "paru" /home/$USER/.local/share/omarchy/bin/  # Confirm replacements
   ```
3. **Ensure executability**:
   ```bash
   sudo chmod +x /home/$USER/.local/share/omarchy/bin/*
   ```
4. **Test**:
   ```bash
   /home/$USER/.local/share/omarchy/bin/omarchy-menu  # Should now work with paru
   ```
Or super+alt+space and Install → AUR or Remove → Package

**Notes**:
- Tested on Omarchy vX.X: AUR packages reappear in menus after this change.
- `paru` supports all `yay` flags (e.g., `--noconfirm`).
- No false positives in other system files.

**Proposed PR**:
I can submit a PR with:
- A script to automate the replacement (e.g., `omarchy-switch-helper`).
- Direct patches to the 4 scripts above.
- Updated documentation in `docs/aur-helper.md`.

**Question for Maintainers**:
- Should the helper name be a variable (e.g., `$AUR_HELPER`) for future flexibility?
- Preferred location for a helper-switching script (if needed)?

*I’m still learning Git/GitHub and bash, so if my issue or future PR needs adjustments, just let me know—I’m happy to improve!*

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

  • Fixed bypr/11826· confirmed

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.