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

Bitwarden menu installation fails after installing Zed

Reported by kvechkanov · filed Aug 16, 2026Closed upstream on 2026-08-16 by its own reporter kvechkanov. GitHub close reason: completed. Closed by its own reporter — not by itself 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

Bitwarden menu installation fails after installing Zedrevision 1 · captured 2026-10-04 12:03 UTC via poll

System details

  • AMD Ryzen 9 5980HS
  • NVIDIA RTX 3050 Ti Mobile + AMD Radeon Graphics
  • Omarchy 4.0.0-1
  • nodejs 26.7.0-1

What's wrong?

Installing Zed and then Bitwarden through the Omarchy menu causes the Bitwarden installation to fail. This can be reproduced using only applications and installation actions offered by Omarchy; Node.js does not need to be installed manually.

The Zed package depends on the repository nodejs and npm packages. The Bitwarden menu action then requests both bitwarden and bitwarden-cli:

omarchy-install-and-launch Bitwarden 'bitwarden bitwarden-cli' bitwarden

bitwarden-cli depends on nodejs-lts-jod, which conflicts with the nodejs package installed for Zed. omarchy-pkg-add invokes pacman with --noconfirm, so pacman automatically selects the default N for replacing nodejs and aborts the entire transaction. The otherwise compatible Bitwarden desktop package is therefore not installed either.

Steps to reproduce

  1. Start without Zed, Bitwarden, or the repository nodejs package installed.
  2. Open the Omarchy menu.
  3. Select Install > Editor > Zed and let the installation complete.
  4. Confirm that Zed pulled in nodejs and npm as dependencies.
  5. Select Install > Service > Bitwarden.
  6. Authenticate when prompted.
  7. Observe the package transaction abort.
  8. Confirm that neither bitwarden nor bitwarden-cli was installed.

Output

:: nodejs-lts-jod-22.23.2-1 and nodejs-26.7.0-1 are in conflict. Remove nodejs? [y/N]
error: unresolvable package conflicts detected
error: failed to prepare transaction (conflicting dependencies)

Expected behavior

Installing one application offered by Omarchy should not prevent another otherwise compatible desktop application from being installed. The optional Bitwarden CLI should not cause the Bitwarden desktop installation to fail.

Possible approaches include installing the desktop package separately, offering the CLI separately, or surfacing the Node.js replacement decision interactively.

Diagnostic output could not be collected because the packaged Omarchy 4.0.0-1 installation does not provide the documented omarchy debug command.

Filed by openai/gpt-5.6-sol via OpenCode.

View raw text
## System details

- AMD Ryzen 9 5980HS
- NVIDIA RTX 3050 Ti Mobile + AMD Radeon Graphics
- Omarchy 4.0.0-1
- nodejs 26.7.0-1

## What's wrong?

Installing Zed and then Bitwarden through the Omarchy menu causes the Bitwarden installation to fail. This can be reproduced using only applications and installation actions offered by Omarchy; Node.js does not need to be installed manually.

The Zed package depends on the repository `nodejs` and `npm` packages. The Bitwarden menu action then requests both `bitwarden` and `bitwarden-cli`:

```text
omarchy-install-and-launch Bitwarden 'bitwarden bitwarden-cli' bitwarden
```

`bitwarden-cli` depends on `nodejs-lts-jod`, which conflicts with the `nodejs` package installed for Zed. `omarchy-pkg-add` invokes `pacman` with `--noconfirm`, so pacman automatically selects the default `N` for replacing `nodejs` and aborts the entire transaction. The otherwise compatible Bitwarden desktop package is therefore not installed either.

### Steps to reproduce

1. Start without Zed, Bitwarden, or the repository `nodejs` package installed.
2. Open the Omarchy menu.
3. Select Install > Editor > Zed and let the installation complete.
4. Confirm that Zed pulled in `nodejs` and `npm` as dependencies.
5. Select Install > Service > Bitwarden.
6. Authenticate when prompted.
7. Observe the package transaction abort.
8. Confirm that neither `bitwarden` nor `bitwarden-cli` was installed.

### Output

```text
:: nodejs-lts-jod-22.23.2-1 and nodejs-26.7.0-1 are in conflict. Remove nodejs? [y/N]
error: unresolvable package conflicts detected
error: failed to prepare transaction (conflicting dependencies)
```

### Expected behavior

Installing one application offered by Omarchy should not prevent another otherwise compatible desktop application from being installed. The optional Bitwarden CLI should not cause the Bitwarden desktop installation to fail.

Possible approaches include installing the desktop package separately, offering the CLI separately, or surfacing the Node.js replacement decision interactively.

Diagnostic output could not be collected because the packaged Omarchy 4.0.0-1 installation does not provide the documented `omarchy debug` command.

Filed by openai/gpt-5.6-sol via OpenCode.

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/12870· confirmed
  • Fixed bypr/14466· confirmed
  • Fixed bypr/14398· confirmed
  • Fixed bypr/11933· 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.