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

omarchy-chromium desktop file breaks OAuth login

Reported by Narsil92 · filed Feb 4, 2026Closed upstream on 2026-02-05 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

omarchy-chromium desktop file breaks OAuth loginrevision 1 · captured 2026-10-04 11:49 UTC via poll

System details

Ryzen 7 3700U, Vega 10, Omarchy 3.3.3

What's wrong?

Hello. So it all started with me trying to log into spotify and oauth window poping in LibreOffice instead of Chromium.

Not gonna lie this bug report was writen with help of AI :)

Package: omarchy-chromium 144.0.7559.132-22
Issue: Template placeholders not replaced in chromium.desktop

Problem

The file /usr/share/applications/chromium.desktop contains unreplaced template variables:
- @@URI_SCHEME@@
- @@EXTRA_DESKTOP_ENTRIES@@

Impact

  • GIO cannot parse the desktop file
  • GNOME portal falls back to incorrect application (LibreOffice)
  • OAuth flows in applications like Spotify fail completely

Fix

Remove the placeholder lines from chromium.desktop

Steps to reproduce

  1. Update to omarchy-chromium 144.0.7559.132-22
  2. Try gio open "https://google.com" - opens LibreOffice instead of Chromium
  3. Try to log into Spotify - fails with LibreOffice opening

Workaround

sudo sed -i '/@@URI_SCHEME@@/d' /usr/share/applications/chromium.desktop
sudo sed -i '/@@EXTRA_DESKTOP_ENTRIES@@/d' /usr/share/applications/chromium.desktop
sudo update-desktop-database /usr/share/applications/
gio mime x-scheme-handler/http chromium.desktop
gio mime x-scheme-handler/https chromium.desktop
View raw text
### System details

Ryzen 7 3700U, Vega 10, Omarchy 3.3.3

### What's wrong?

Hello.  So it all started with me trying to log into spotify and oauth window poping in LibreOffice instead of Chromium.

Not gonna lie this bug report was writen with help of AI :) 


**Package:** omarchy-chromium 144.0.7559.132-22
**Issue:** Template placeholders not replaced in chromium.desktop

## Problem
The file `/usr/share/applications/chromium.desktop` contains unreplaced template variables:
- `@@URI_SCHEME@@`
- `@@EXTRA_DESKTOP_ENTRIES@@`

## Impact
- GIO cannot parse the desktop file
- GNOME portal falls back to incorrect application (LibreOffice)
- OAuth flows in applications like Spotify fail completely

## Fix
Remove the placeholder lines from chromium.desktop

## Steps to reproduce
1. Update to omarchy-chromium 144.0.7559.132-22
2. Try `gio open "https://google.com"` - opens LibreOffice instead of Chromium
3. Try to log into Spotify - fails with LibreOffice opening

## Workaround
```bash
sudo sed -i '/@@URI_SCHEME@@/d' /usr/share/applications/chromium.desktop
sudo sed -i '/@@EXTRA_DESKTOP_ENTRIES@@/d' /usr/share/applications/chromium.desktop
sudo update-desktop-database /usr/share/applications/
gio mime x-scheme-handler/http chromium.desktop
gio mime x-scheme-handler/https chromium.desktop

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.