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.
Installation fails with gpg error
Reported by abradburne · filed Jul 14, 2025Closed upstream on 2025-07-16 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
Near the end of omarchy installation, it fails with a gpg error when attempting to install dropbox, Spotify and 1password-beta
:: (10/10) Parsing SRCINFO: localsend-bin
gpg: directory '/home/alan/.gnupg' created
gpg: /home/alan/.gnupg/trustdb.gpg: trustdb
gpg: error reading key: No public key
gpg: error reading key: No public key
gpg: error reading key: No public key
:: PGP keys need importing:
→ 1C61A2656FB57B7E4DE0F4C1FC918B335044912E, required by: dropbox
→ B420FD3777CCE3A7F0076B55C85668DF69375001, required by: spotify
→ 3FEF9748469ADBE15DA7CA80AC2D62742012EA22, required by: 1password-beta
:: Importing keys with gpg...
gpg: keyserver receive failed: No route to host
→ problem importing keys
Omarchy installation failed! You can retry by running: source ~/.local/share/omarchy/install.shI have tried multiple times with a clean Arch install and same result every time.
I removed them from xtras.sh to get the install to complete.
Then when I boot into Omarchy and attempt to manually install, I get the same.
There are reports of other people getting "Server indicated a failure" from the keyserver too.
Despite being able to connect via ssl to keyserver.ubuntu.com, gpg can't get keys from it.
So I ended up manually importing a key from pgp.mit.edu instead and that worked fine.
gpg --keyserver hkps://pgp.mit.edu --recv-keys <key>
I set keyserver pgp.mit.edu in ~/.gnupg/gpg.conf and could then install the other packages fine.
I guess it's an ubuntu issue, possibly geographically affected (I'm in Japan) - not sure if there's a better alternative to the ubuntu keyserver, but hopefully useful for others affected by this issue.
View raw text
Near the end of omarchy installation, it fails with a gpg error when attempting to install dropbox, Spotify and 1password-beta ``` :: (10/10) Parsing SRCINFO: localsend-bin gpg: directory '/home/alan/.gnupg' created gpg: /home/alan/.gnupg/trustdb.gpg: trustdb gpg: error reading key: No public key gpg: error reading key: No public key gpg: error reading key: No public key :: PGP keys need importing: → 1C61A2656FB57B7E4DE0F4C1FC918B335044912E, required by: dropbox → B420FD3777CCE3A7F0076B55C85668DF69375001, required by: spotify → 3FEF9748469ADBE15DA7CA80AC2D62742012EA22, required by: 1password-beta :: Importing keys with gpg... gpg: keyserver receive failed: No route to host → problem importing keys Omarchy installation failed! You can retry by running: source ~/.local/share/omarchy/install.sh ``` I have tried multiple times with a clean Arch install and same result every time. I removed them from xtras.sh to get the install to complete. Then when I boot into Omarchy and attempt to manually install, I get the same. There are reports of other people getting "Server indicated a failure" from the keyserver too. Despite being able to connect via ssl to keyserver.ubuntu.com, gpg can't get keys from it. So I ended up manually importing a key from pgp.mit.edu instead and that worked fine. `gpg --keyserver hkps://pgp.mit.edu --recv-keys <key>` I set `keyserver pgp.mit.edu` in `~/.gnupg/gpg.conf` and could then install the other packages fine. I guess it's an ubuntu issue, possibly geographically affected (I'm in Japan) - not sure if there's a better alternative to the ubuntu keyserver, but hopefully useful for others affected by this issue.
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.