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.
1Password 2FA Code fails to save
Reported by opswole · filed Jul 5, 2025Closed upstream on 2025-07-09 by dhh. GitHub close reason: completed. No closing PR or commit is recorded — "completed" alone is not 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
Signing in to 1Password with MFA configured on the 1Password account itself produces:
"1Password was unable to save your two-factor token"
The logs show it as:
WARN 2025-07-05T20:51:12.093+00:00 runtime-worker(ThreadId(8)) [1P:op-b5-client/src/internal/unauthorized_session/auth_flow.rs:901] Failed to save an account's 2FA token with an error of SystemKeyringError(LinuxError(DBus(MethodError(OwnedErrorName(ErrorName(Str(Owned("org.freedesktop.DBus.Error.ServiceUnknown")))), Some("The name is not activatable"), Msg { type: Error, sender: UniqueName(Str(Borrowed("org.freedesktop.DBus"))), reply-serial: 2, body: Signature("s") })))). 2FA will only be valid for this unlock session!As far as I can tell Arch doesn't ship with a keychain by default.
Someone in the discord solved it via:
# Add gnome-keyring
yay -S gnome-keyring
# Store something to initialize a default keyring
secret-tool store --label="test" test test
# Remove test val
secret-tool clear test testkwallet-pam being installed seems to solve it too.
View raw text
Signing in to 1Password with MFA configured on the 1Password account itself produces:
"1Password was unable to save your two-factor token"
The logs show it as:
```bash
WARN 2025-07-05T20:51:12.093+00:00 runtime-worker(ThreadId(8)) [1P:op-b5-client/src/internal/unauthorized_session/auth_flow.rs:901] Failed to save an account's 2FA token with an error of SystemKeyringError(LinuxError(DBus(MethodError(OwnedErrorName(ErrorName(Str(Owned("org.freedesktop.DBus.Error.ServiceUnknown")))), Some("The name is not activatable"), Msg { type: Error, sender: UniqueName(Str(Borrowed("org.freedesktop.DBus"))), reply-serial: 2, body: Signature("s") })))). 2FA will only be valid for this unlock session!
```
As far as I can tell Arch doesn't ship with a keychain by default.
Someone in the discord solved it via:
```bash
# Add gnome-keyring
yay -S gnome-keyring
# Store something to initialize a default keyring
secret-tool store --label="test" test test
# Remove test val
secret-tool clear test test
```
kwallet-pam being installed seems to solve it too.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.