Proof Portal

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

Install > AUR shouldn't close TUI window if exit !=0

Reported by wrex · filed Sep 9, 2025Closed upstream on 2025-09-09 by dhh. GitHub close reason: completed. No closing PR or commit is recorded — "completed" alone is not evidence of a fix.

Open at source

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

Install > AUR shouldn't close TUI window if exit !=0revision 1 · captured 2026-10-04 11:35 UTC via poll

System details

AMD Ryzen AI 9 MX 370 / Omarchy v2.0.5 (offline iso)

What's wrong?

Attempted to install sabaki via SUPER-ALT-SPACE Install > AUR

Seemed to install okay, but couldn't find sabaki anywhere in my $PATH or via the menus. Wasn't clear to me that yay -S was the command that the menu was running, but when I ran yay -S sabaki in the terminal it was obvious that the install had failed with an error:

TypeError: Function.prototype.apply was called on undefined, which is a undefined and not a function
    at node:internal/main/run_main_module:33:47

Node.js v24.7.0
==> ERROR: A failure occurred in check().
    Aborting...
 -> error making: sabaki-exit status 4
 -> Failed to install the following packages. Manual intervention is required:
sabaki - exit status 4

When I used the menu to run the command, the window closed immediately after completion. It wasn't at all obvious that the install had failed. I thought maybe it had installed it in an unknown location or installed with a different name for the executable, so I asked a question on discord. It now appears that it had failed (silently).

Expected result: some sort of indication that the install had failed.

Issue was discussed here: https://discord.com/channels/1390012484194275541/1390012487000395859/1414800655734018111

Frankly, I'm disheartened by the attitudes of some of the people on discord. I could have just accepted that the GUI didn't work and installed the executable myself in a terminal window, but when I asked what might be happening I was derided by the users there.

This is the most interesting linux distribution I've seen in years. It's disheartening when the recommended support portal effectively tells people to use the terminal and fix it yourself.

View raw text

### System details

AMD Ryzen AI 9 MX 370 / Omarchy v2.0.5 (offline iso)

### What's wrong?

Attempted to install `sabaki` via SUPER-ALT-SPACE `Install` > `AUR`

Seemed to install okay, but couldn't find sabaki anywhere in my $PATH or via the menus. Wasn't clear to me that `yay -S` was the command that the menu was running, but when I ran `yay -S sabaki` in the terminal it was obvious that the install had failed with an error:

```
TypeError: Function.prototype.apply was called on undefined, which is a undefined and not a function
at node:internal/main/run_main_module:33:47

Node.js v24.7.0
==> ERROR: A failure occurred in check().
Aborting...
-> error making: sabaki-exit status 4
-> Failed to install the following packages. Manual intervention is required:
sabaki - exit status 4
```

Expected result: some sort of indication that the install had failed.

Issue was discussed here: https://discord.com/channels/1390012484194275541/1390012487000395859/1414800655734018111

This is the most interesting linux distribution I've seen in years. It's disheartening when the recommended support portal effectively tells people to use the terminal and fix it yourself.

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.

Proof

History & reports

Reference