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-3901GitHub issuePublicReceived

omarchy-update fails at Searching AUR for updates when folder already exists(?)

Reported by Amoodaa · filed Dec 17, 2025Closed upstream on 2026-02-02 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

omarchy-update fails at Searching AUR for updates when folder already exists(?)revision 1 · captured 2026-10-04 11:49 UTC via poll

System details

during 3.2.4 update, 13620H RTX4050 laptop

What's wrong?

Updating these manually after deleting the repos would work, but its unclear why i need to do that, am i doing something wrong?

Running as unit: run-p238361-i238362.service; invocation ID: 7a16142e075146ae80fa049fd3028406

Update AUR packages
:: Searching AUR for updates...
 -> Orphan (unmaintained) AUR Packages: activitywatch
:: 2 packages to upgrade/install.
2  aur/google-chrome     143.0.7499.109-1 -> 143.0.7499.146-1
1  aur/google-cloud-cli  549.0.1-1        -> 550.0.0-1
==> Packages to exclude: (eg: "1 2 3", "1-3", "^4" or repo name)
 -> Excluding packages may cause partial upgrades and break systems
==>
AUR Explicit (2): google-chrome-143.0.7499.146-1, google-cloud-cli-550.0.0-1
:: (0/2) Failed to download PKGBUILD: google-cloud-cli
:: (1/2) Downloaded PKGBUILD: google-chrome
 -> error fetching google-cloud-cli: fatal: destination path 'google-cloud-cli' already exists and is not an empty directory.
         context: exit status 128


Something went wrong during the update!

Please review the output above carefully, correct the error, and retry the update.

If you need assistance, get help from the community at https://omarchy.org/discord

🌎 Done! Press any key to close...
View raw text
### System details

during 3.2.4 update, 13620H RTX4050 laptop 

### What's wrong?

Updating these manually after deleting the repos would work, but its unclear why i need to do that, am i doing something wrong?

```
Running as unit: run-p238361-i238362.service; invocation ID: 7a16142e075146ae80fa049fd3028406

Update AUR packages
:: Searching AUR for updates...
 -> Orphan (unmaintained) AUR Packages: activitywatch
:: 2 packages to upgrade/install.
2  aur/google-chrome     143.0.7499.109-1 -> 143.0.7499.146-1
1  aur/google-cloud-cli  549.0.1-1        -> 550.0.0-1
==> Packages to exclude: (eg: "1 2 3", "1-3", "^4" or repo name)
 -> Excluding packages may cause partial upgrades and break systems
==>
AUR Explicit (2): google-chrome-143.0.7499.146-1, google-cloud-cli-550.0.0-1
:: (0/2) Failed to download PKGBUILD: google-cloud-cli
:: (1/2) Downloaded PKGBUILD: google-chrome
 -> error fetching google-cloud-cli: fatal: destination path 'google-cloud-cli' already exists and is not an empty directory.
         context: exit status 128


Something went wrong during the update!

Please review the output above carefully, correct the error, and retry the update.

If you need assistance, get help from the community at https://omarchy.org/discord

🌎 Done! Press any key to close...
```

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.