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

[Bug] Persistent Keyring prompt on every Brave browser launch.

Reported by vaqMAD · filed Oct 4, 2025Closed upstream on 2025-10-26 by ryanrhughes. GitHub close reason: completed. No closing PR or commit is recorded — "completed" alone is not evidence of a fix.

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

[Bug] Persistent Keyring prompt on every Brave browser launch.revision 1 · captured 2026-10-04 11:35 UTC via poll

System details

AMD Ryzen 7 7800X3D, NVIDIA 4080 SUPER, Omarchy Latest (3.0.2)

What's wrong?

On every launch, Brave prompts for the GNOME Keyring password.
Brave belongs to the same keyring as the default Chromium. Chromium does not ask for access to keyring, but Brave does. I don't know why. I checked the flag settings, as well as the configuration files for both browsers - everything seems to be identical.

Brave Version : 1.83.109 Chromium: 141.0.7390.55 (Official Build) (64-bit)
Chromium Version: 140.0.7339.207 (Official Build)

Note
From what I can see, I'm not the only struggling wit this problem: https://discord.com/channels/1390012484194275541/1421504252299186208

Might be related to : https://github.com/basecamp/omarchy/issues/1015


<img width="1261" height="693" alt="Image" src="https://github.com/user-attachments/assets/5f6d551f-e4bf-400f-b631-87c73582f4f9" />

View raw text
### System details

AMD Ryzen 7 7800X3D, NVIDIA 4080 SUPER, Omarchy Latest (3.0.2)

### What's wrong?

On every launch, Brave prompts for the GNOME Keyring password.
**Brave belongs to the same keyring as the default Chromium**.  Chromium does not ask for access to keyring, but Brave does. I don't know why. I checked the flag settings, as well as the configuration files for both browsers - everything seems to be identical. 

Brave Version : 	1.83.109 Chromium: 141.0.7390.55 (Official Build) (64-bit) 
Chromium Version:  140.0.7339.207 (Official Build)

**Note**
From what I can see, I'm not the only struggling wit this problem: https://discord.com/channels/1390012484194275541/1421504252299186208

Might be related to : https://github.com/basecamp/omarchy/issues/1015


--- 

<img width="1261" height="693" alt="Image" src="https://github.com/user-attachments/assets/5f6d551f-e4bf-400f-b631-87c73582f4f9" />
  • 5f6d551f-e4bf-400f-b631-87c73582f4f9

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.