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

Obsidian CLI fails due to malformed -disable-gpu in default user flags

Reported by acsezen · filed Oct 1, 2026Closed upstream on 2026-10-01 by its own reporter acsezen, as a duplicate of #8538 (R-1382). GitHub close reason: duplicate.

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

Obsidian CLI fails due to malformed -disable-gpu in default user flagsrevision 1 · captured 2026-10-04 12:17 UTC via poll

Description

Omarchy's default config/obsidian/user-flags.conf contains -disable-gpu (one leading dash) instead of --disable-gpu.

The Arch Obsidian launcher reads this file from ~/.config/obsidian/user-flags.conf and passes its contents to Electron. Obsidian interprets the malformed flag as a CLI command, causing the following error:

Error: Command "-disable-gpu" not found. It may require a plugin to be enabled.

Steps to reproduce

  1. Use Omarchy's default Obsidian user flags:
   # Obsidian reads this file through the Arch package wrapper.
   -disable-gpu
   --enable-wayland-ime
  1. With Obsidian already running and its CLI enabled, run obsidian in a terminal.
  2. Observe the error above. The command exits with status 0 despite reporting an error.

Expected behavior

The launcher should not pass a malformed GPU flag that Obsidian interprets as an application command.

Verification and suggested fix

The typo is present in both the installed Omarchy template /usr/share/omarchy/config/obsidian/user-flags.conf (line 2) and the user config ~/.config/obsidian/user-flags.conf.

The package launcher /usr/bin/obsidian invokes:

exec electron43 /usr/lib/obsidian/app.asar $OBSIDIAN_USER_FLAGS "$@"

Bypassing the wrapper and supplying the correctly spelled flag:

electron43 /usr/lib/obsidian/app.asar --disable-gpu --enable-wayland-ime help

returns normal Obsidian CLI help with exit status 0, without the command-not-found error.

Change -disable-gpu to --disable-gpu in config/obsidian/user-flags.conf. Existing installations with the old flag also need their user config corrected.

Environment

Verified using omarchy version and pacman -Q obsidian electron43:

  • Omarchy: 4.0.4-1
  • Obsidian: 1.13.7-2
  • Electron: electron43 43.6.0-1
  • Arch Linux, Wayland session
View raw text
## Description

Omarchy's default `config/obsidian/user-flags.conf` contains `-disable-gpu` (one leading dash) instead of `--disable-gpu`.

The Arch Obsidian launcher reads this file from `~/.config/obsidian/user-flags.conf` and passes its contents to Electron. Obsidian interprets the malformed flag as a CLI command, causing the following error:

```text
Error: Command "-disable-gpu" not found. It may require a plugin to be enabled.
```

## Steps to reproduce

1. Use Omarchy's default Obsidian user flags:
   ```text
   # Obsidian reads this file through the Arch package wrapper.
   -disable-gpu
   --enable-wayland-ime
   ```
2. With Obsidian already running and its CLI enabled, run `obsidian` in a terminal.
3. Observe the error above. The command exits with status 0 despite reporting an error.

## Expected behavior

The launcher should not pass a malformed GPU flag that Obsidian interprets as an application command.

## Verification and suggested fix

The typo is present in both the installed Omarchy template `/usr/share/omarchy/config/obsidian/user-flags.conf` (line 2) and the user config `~/.config/obsidian/user-flags.conf`.

The package launcher `/usr/bin/obsidian` invokes:

```bash
exec electron43 /usr/lib/obsidian/app.asar $OBSIDIAN_USER_FLAGS "$@"
```

Bypassing the wrapper and supplying the correctly spelled flag:

```bash
electron43 /usr/lib/obsidian/app.asar --disable-gpu --enable-wayland-ime help
```

returns normal Obsidian CLI help with exit status 0, without the command-not-found error.

Change `-disable-gpu` to `--disable-gpu` in `config/obsidian/user-flags.conf`. Existing installations with the old flag also need their user config corrected.

## Environment

Verified using `omarchy version` and `pacman -Q obsidian electron43`:

- Omarchy: `4.0.4-1`
- Obsidian: `1.13.7-2`
- Electron: `electron43 43.6.0-1`
- Arch Linux, Wayland session

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.