Proof Portal
Omarchy
ProbeLabs65 findings · 95 requirementsA 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.
[Bug]: Brave often forgetting my logged in session and prompting for keyring
Reported by NicolasDorier · filed Jan 19, 2026Closed upstream on 2026-02-08 by its own reporter NicolasDorier. GitHub close reason: completed. Closed by its own reporter — not by itself evidence of a fix.
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
System details
Omarchy 3.3.3
What's wrong?
It may be a Brave bug, but this is a VERY annoying behavior that might make me switch browser.
Everything run fine for a while, then out of the blue, after a reboot a popup appears to create a new keyring.
After continuing, all my logged in sessions are forgotten. I need to re-log to everything.
Not every reboot trigger this issue. It happens sometimes after reboot, without a clear trigger.
The popup sometimes open in special workspaces and I need to hunt for it. If I ignore it, no Brave windows (or web app window) will open. Also, omarchy will need hard restart, this popup prevent reboot.
I noticed that it keeps creating .keyring files in ~/.local/share/keyrings:
1. Default.keyring,
2. Then Default_keyring.keyring,
3. Then Default_keyring_1.keyring etc...
I attempted to replace the new keyring by the old one (for example, copying Default.keyring to Default_keyring_1.keyring) and restarted Brave. When Brave restarts, no prompt is asked, but the file get rewritten.
I've noticed that cookies in Brave were all recent. So it seems Brave corrupted the Cookie database or something and recreated it from scratch.
sqlite3 ~/.config/BraveSoftware/Brave-Browser/Default/CookiesOutside of this, all my history, bookmarks and everything is intact. But I need to re-log to everything.
This happens several time per week.
Workaround
Edit .config/brave-flags.conf and add --password-store=basic, reboot.
This will configure brave to not depend on Gnome keyring.
After implementing this workaround, the bug happened again using Ente Auth, which use Gnome keyring. However, I didn't lost my logged in session with Brave.
Probably a bug with gnome keyring.
Related issues
https://github.com/basecamp/omarchy/issues/2203
https://www.reddit.com/r/omarchy/comments/1njl8cm/what_does_it_mean_when_i_launch_brave_browser_and/
https://community.brave.app/t/keyrings-problem/639163 (this one create a password popup... for mine, the popup is about setting up password for a new keyring similar to this)
https://www.reddit.com/r/omarchy/comments/1qgtkt0/default_keyring_issue_omarchy/ (This one seems to show it happens with Chrome as well?)
View raw text
### System details Omarchy 3.3.3 ### What's wrong? It may be a Brave bug, but this is a VERY annoying behavior that might make me switch browser. Everything run fine for a while, then out of the blue, after a reboot [a popup appears to create a new keyring](https://www.reddit.com/r/omarchy/comments/1njl8cm/what_does_it_mean_when_i_launch_brave_browser_and/). After continuing, all my logged in sessions are forgotten. I need to re-log to everything. Not every reboot trigger this issue. It happens sometimes after reboot, without a clear trigger. The popup sometimes open in special workspaces and I need to hunt for it. If I ignore it, no Brave windows (or web app window) will open. Also, omarchy will need hard restart, this popup prevent reboot. I noticed that it keeps creating .keyring files in `~/.local/share/keyrings`: 1. Default.keyring, 2. Then Default_keyring.keyring, 3. Then Default_keyring_1.keyring etc... I attempted to replace the new keyring by the old one (for example, copying `Default.keyring` to `Default_keyring_1.keyring`) and restarted Brave. When Brave restarts, no prompt is asked, but the file get rewritten. I've noticed that cookies in Brave were all recent. So it seems Brave corrupted the Cookie database or something and recreated it from scratch. ```bash sqlite3 ~/.config/BraveSoftware/Brave-Browser/Default/Cookies ``` Outside of this, all my history, bookmarks and everything is intact. But I need to re-log to everything. This happens several time per week. ### Workaround Edit `.config/brave-flags.conf` and add `--password-store=basic`, reboot. This will configure brave to not depend on Gnome keyring. After implementing this workaround, the bug happened again using `Ente Auth`, which use Gnome keyring. However, I didn't lost my logged in session with Brave. Probably a bug with gnome keyring. ### Related issues https://github.com/basecamp/omarchy/issues/2203 https://www.reddit.com/r/omarchy/comments/1njl8cm/what_does_it_mean_when_i_launch_brave_browser_and/ https://community.brave.app/t/keyrings-problem/639163 (this one create a password popup... for mine, the popup is about setting up password for a new keyring similar to [this](https://www.reddit.com/r/omarchy/comments/1njl8cm/what_does_it_mean_when_i_launch_brave_browser_and/)) https://www.reddit.com/r/omarchy/comments/1qgtkt0/default_keyring_issue_omarchy/ (This one seems to show it happens with Chrome as well?)
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.