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

Gnome-keyring not creating default keyvault, 1Password MFA issues

Reported by jzetterman · filed Jul 26, 2025Closed upstream on 2025-11-03 by dhh, as not planned.

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

Gnome-keyring not creating default keyvault, 1Password MFA issuesrevision 1 · captured 2026-10-04 11:27 UTC via poll

I use MFA with 1Password and by default it doesn't appear that gnome-keyring is set up to work with Hyprland fully. 1Password is unable to save the token after I enter my MFA code (on my personal account) or after I complete a Duo MFA (on my work account) challenge.

Specifically, when logging in it's not (at least on my system) initializing a default keyring (I have no keyrings at all). I was able to prove this by checking ~/.local/share/keyrings/, which is empty as well as running secret-tool store --label="Test" testkey testvalue which prompts me to set a password for "Default keyring". I see that gnome-keyring was added to the Yay install command in xtras.sh at some point and that a migration file exists to add it to older installations. I've replicated this on multiple virtual machines as well.

Creating a keyring with Seahorse and making it the default does allow 1Password to save the MFA tokens. However, that keyring does not automatically unlock when first logging into the system.

I'm investigating steps to effectively address this on an alternate and virtual machines. So far I've only succeeded in breaking LUKS encryption and bricking the install. That said, I hope to develop a solution this weekend.

View raw text
I use MFA with 1Password and by default it doesn't appear that gnome-keyring is set up to work with Hyprland fully. 1Password is unable to save the token after I enter my MFA code (on my personal account) or after I complete a Duo MFA (on my work account) challenge. 

Specifically, when logging in it's not (at least on my system) initializing a default keyring (I have no keyrings at all). I was able to prove this by checking ~/.local/share/keyrings/, which is empty as well as running `secret-tool store --label="Test" testkey testvalue` which prompts me to set a password for "Default keyring". I see that gnome-keyring was added to the Yay install command in xtras.sh at some point and that a migration file exists to add it to older installations. I've replicated this on multiple virtual machines as well. 

Creating a keyring with Seahorse and making it the default does allow 1Password to save the MFA tokens. However, that keyring does not automatically unlock when first logging into the system.

I'm investigating steps to effectively address this on an alternate and virtual machines. So far I've only succeeded in breaking LUKS encryption and bricking the install. That said, I hope to develop a solution this weekend. 

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.