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

Bitwarden installation fails due to nodejs / nodejs-lts-jod conflict

Reported by dzintars-co · filed Sep 21, 2026 · open at source

In the audited area (menu) — decided by arbitration. Not validated 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?
AreaIn the audited areamenu· Decided by arbitration
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. So far: in the audited area (menu) — decided by arbitration; matches no known issue — decided by agents · verified. The outcome (valid, duplicate, not a bug, …) is not decided yet. See the decision.

Original report

Bitwarden installation fails due to nodejs / nodejs-lts-jod conflictrevision 1 · captured 2026-09-28 21:23 UTC via poll
omarchy-install-and-launch Bitwarden 'bitwarden bitwarden-cli' bitwarden

bitwarden-cli currently requires nodejs-lts-jod, which conflicts with the already installed nodejs 26.8.1-2.

Actual result

:: nodejs-lts-jod-22.23.2-1 and nodejs-26.8.1-2 are in conflict.
Remove nodejs? [y/N]

error: unresolvable package conflicts detected
error: failed to prepare transaction (conflicting dependencies)
:: nodejs-lts-jod-22.23.2-1 and nodejs-26.8.1-2 are in conflict

The installation then stops and Bitwarden is not installed.

Expected behavior

Installing Bitwarden from the Omarchy menu should not require removing an existing Node.js installation.

The desktop Bitwarden package should still be installable even if bitwarden-cli has a conflicting Node.js dependency.

Possible solution

Install bitwarden separately and make bitwarden-cli optional, or detect the Node.js conflict before trying to install the CLI.

Screenshot attached.

<img width="982" height="695" alt="Image" src="https://github.com/user-attachments/assets/0d2e9d3f-a052-4772-990d-562e6137f35d" />

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

`bitwarden-cli` currently requires `nodejs-lts-jod`, which conflicts with the already installed `nodejs 26.8.1-2`.

## Actual result

```text
:: nodejs-lts-jod-22.23.2-1 and nodejs-26.8.1-2 are in conflict.
Remove nodejs? [y/N]

error: unresolvable package conflicts detected
error: failed to prepare transaction (conflicting dependencies)
:: nodejs-lts-jod-22.23.2-1 and nodejs-26.8.1-2 are in conflict
```

The installation then stops and Bitwarden is not installed.

## Expected behavior

Installing Bitwarden from the Omarchy menu should not require removing an existing Node.js installation.

The desktop Bitwarden package should still be installable even if `bitwarden-cli` has a conflicting Node.js dependency.

## Possible solution

Install `bitwarden` separately and make `bitwarden-cli` optional, or detect the Node.js conflict before trying to install the CLI.

Screenshot attached.

<img width="982" height="695" alt="Image" src="https://github.com/user-attachments/assets/0d2e9d3f-a052-4772-990d-562e6137f35d" />
  • 0d2e9d3f-a052-4772-990d-562e6137f35d

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.

  • Decided by arbitration: in the audited area (menu)
  • Decided by agents · verified: matches no known issue

The outcome (valid, duplicate, not a bug, …) is not decided yet.