Repository navigation
Description
Summary
Omarchy already diagnosed this exact failure and fixed it — for browsers only. Every other Electron app is still exposed, including Signal, which Omarchy itself installs.
migrations/1784508556.sh says it plainly:
Chromium-based browsers auto-detect their os_crypt backend; on Hyprland the xdg-desktop-portal Secret backend has no provider and fails, so they can fall back to the 'basic' (v10) store. A swap from the gnome-libsecret (v11) key to the basic key makes existing cookies and saved passwords undecryptable, so the browser silently drops them and the user is logged out of everything.
That migration pins --password-store=gnome-libsecret, but only into:
~/.config/{chromium,brave,chrome,microsoft-edge-stable}-flags.conf
Electron apps are not Chromium browsers, but they use the same os_crypt/safeStorage machinery and the same flag. signal-desktop even reads the same style of file — from /usr/bin/signal-desktop:
SIGNAL_USER_FLAGS_FILE="${XDG_CONFIG_HOME:-$HOME/.config}/signal-desktop-flags.conf"Nothing in Omarchy writes it, so the fallback the migration exists to prevent still happens — with the same consequence, one app over.
What happened
Signal profile carried onto an Omarchy machine during a migration. On launch:
Detected change in safeStorage backend, can't decrypt DB key
(previous: gnome_libsecret, current: basic_text)
ERROR CORE sqlcipher_page_cipher: hmac check failed for pgno=1
ERROR CORE sqlite3Codec: error decrypting page 1 data: 1
The app opens to an unusable state. XDG_CURRENT_DESKTOP=Hyprland, gnome-keyring-daemon running and serving org.freedesktop.secrets, and the package is intact (pacman -Qkk signal-desktop → 175 files, 0 altered), so this is not packaging corruption or a missing secret service — purely the backend fallback.
Steps to reproduce
- On a machine with a working keyring, use
signal-desktopso its DB key is stored undergnome_libsecret. - Copy
~/.config/Signalto an Omarchy/Hyprland machine. - Launch Signal.
Expected: it decrypts and opens. Actual: basic_text is selected, the DB key cannot be decrypted, and the profile is unrecoverable without the original keyring secret.
Fix
echo '--password-store=gnome-libsecret' >> ~/.config/signal-desktop-flags.confConfirmed: with the flag the safeStorage warning disappears immediately, and after re-linking, a quit-and-relaunch cycle shows zero decrypt errors and zero backend complaints — i.e. the pin is what makes it survive restarts.
Suggested change: extend 1784508556.sh's loop (and whatever ships defaults) to the Electron apps Omarchy installs or launches — omarchy-install-service-signal at minimum, and worth auditing 1password and spotify alongside it. The browser list is an allowlist where the underlying problem is not browser-specific.
Worth noting the browser fix is the gentler case: a browser silently drops cookies and logs you out. For Signal the profile is simply unrecoverable — the local message history is gone and the device must be re-linked.
Related
- default-keyring.sh writes an unparseable stub keyring, wiping Chrome/Docker secrets on every login #9235 (
default-keyring.shwrites an unparseable stub keyring) and Update/reboot left keyring in invalid state, browser sessions and gh auth got cleared #5105 (keyring left invalid after update) — both about the keyring itself; this one is about apps not being pinned to it. - After installing VSCode and login in to GitHub there's a missing OS keyring error #1015 (closed) — VS Code / missing OS keyring, likely the same root cause in another Electron app.
System
- Omarchy 4.0.2-1
- Hyprland 0.56.2,
XDG_CURRENT_DESKTOP=Hyprland - signal-desktop 8.24.1-1
- gnome-keyring 1:50.0-1, libsecret 0.21.7-1
- Kernel 7.1.9-arch1-2, AMD Ryzen AI 9 HX 370 / Radeon 890M
Activity
matt8poi commentedon Sep 9, 2026
Same root cause, but there is a second class of app the suggested fix would miss, and a failure mode that does not need a migrated profile.
Shared-Electron apps read a different file
The apps listed here (signal-desktop, spotify, 1password) each bundle their own Electron and read a per-app flags file. Arch also ships shared Electron packages, where
/usr/bin/electronNNreads:An allowlist of per-app files will not reach these. For some of them there is no per-app file to write to at all —
/usr/bin/element-desktopis the entire wrapper:so
~/.config/electron{43,}-flags.confis the only place the pin can go.obsidianis in this class too, and is shipped ininstall/omarchy-base.packages(depends onelectron43, has a SUPER+SHIFT+O binding and a theme template).Hard-fails on a clean install, no migration needed
This is not only a migration hazard. On a fresh Omarchy 4.0.3 machine with no prior profile,
element-desktopwill not start at all. Electron selectsbasic_text, and Element refuses to run on it:Repro is just
sudo pacman -S element-desktopand launch it. gnome-keyring is running andorg.freedesktop.secretsis registered on the session bus, so the keyring itself is fine — Electron never asks for it.Same fix:
--password-store=gnome-libsecretin~/.config/electron43-flags.conf. Element then logsUsing storage mode 'encrypted' with backend 'gnome_libsecret'and records the choice.Implementation trap for whoever fixes this
/usr/bin/electronNNselects its flags file withelif:So backfilling the generic
electron-flags.confsilently does nothing for anyone who already has a versionedelectronNN-flags.conf. The generic file is otherwise the better target: it survives the electron43 → electron44 bump, and shipping it asconfig/electron-flags.confwould make it reachable viaomarchy refresh config, the waychromium-flags.confalready is.System
Omarchy 4.0.3-1 (stable), Hyprland 0.56.2-2, element-desktop 1.12.25-1, electron43 43.6.0-1, obsidian 1.13.7-2, gnome-keyring 1:50.0-1, libsecret 0.21.7-1, kernel 7.2.3-arch1-3,
XDG_CURRENT_DESKTOP=Hyprland.Filed by Claude Opus 5 via Claude Code.
omarchybot commentedon Oct 11, 2026
Checked against current
quattro: nothing pins the password store for Signal or for Arch's shared Electron. The only pins are the browser ones (config/chromium-flags.conf,migrations/1784508556.sh) and the VS Code setting inbin/omarchy-install-editor-vscode. The mechanism you describe is real, and both parts of this report already have an open fix:--password-store=gnome-libsecretto~/.config/signal-desktop-flags.confbefore the first launch fromomarchy-install-service-signal, and adds a migration for existing installs. It was verified on a Hyprland worker with Signal 8.26.0. Agnome_libsecretprofile failed to decrypt without the pin, opened after the migration, and failed again once the pin was removed.config/electron-flags.confand pinselectron-flags.confalong with any versionedelectronNN-flags.confthat would shadow it./usr/bin/obsidianlaunches throughelectron43, so this also covers Obsidian, which Omarchy installs by default. It does not reach Signal, which bundles its own Electron and reads its own flags file. So Pin Electron password store to gnome-libsecret #10346 is not linked as closing this issue: if it merged on its own, it would close the issue with Signal still broken.The two pull requests complement each other rather than compete, and each is reviewed as its own item. Neither touches 1Password or Spotify, and there is no evidence yet that either app hits this failure, so they stay as audit candidates.
Reviewed by Claude Opus 5.5, with a second opinion from Codex Medium. Codex agreed on the mechanism and on keeping the two fixes separate; it did not run independently of this review. Nothing was run for this issue itself. Merging #10018 and #10346 is the maintainer's call.
e2goon commentedon Oct 18, 2026
Claude Desktop hits this too, and neither open fix reaches it.
claude-desktop2.42304.0-1 from the Omarchy repo bundles its own Electron and starts through/usr/bin/claude-desktop. That launcher reads~/.config/claude-desktop-flags.confand adds--ozone-platform=wayland, but no--password-store. On Hyprland it falls back tobasic_text, so the sign-in is never saved and I have to log in again after every restart. From~/.config/Claude/logs/main.log:Local Statehas"os_crypt":{"portal":{"prev_desktop":"Hyprland","prev_init_success":false}}, the same failuremigrations/1784508556.shdescribes for browsers.#10018 and #10346 don't cover it, since it reads neither
signal-desktop-flags.confnorelectron-flags.conf. omacom/omarchy-pkgs#274 had a launcher that pinnedgnome-libsecret, but it was closed in favor of omacom/omarchy-pkgs#348, and the launcher shipped now doesn't have the pin.Workaround:
Omarchy 4.0.4-1, Hyprland 0.56.2-4, gnome-keyring 1:51.1-1 (running), libsecret 0.21.8.2-1,
XDG_CURRENT_DESKTOP=Hyprland.omarchybot commentedon Oct 18, 2026
Checked the Claude Desktop report against
omacom/omarchy-pkgsmaster. The launcher it ships at/usr/bin/claude-desktop(pkgbuilds/claude-desktop/claude-desktop-launcher.sh) reads~/.config/claude-desktop-flags.confand adds--ozone-platform=waylandon Wayland, but never passes--password-store. So unless the user has added the flag, Electron picks its own backend, which fits thebasic_textline in your log. Neither open fix reaches it: #10018 writessignal-desktop-flags.conf, and #10346 covers Arch's sharedelectronNNwrappers, which this bundled Electron doesn't go through.omarchy-pkgs#274 did pin
gnome-libsecretin its launcher. It was closed because #348 had already shipped the package, not because the pin was rejected, and #348's launcher was modelled on the ChatGPT one, which has no pin either. In the same repository,hermes-desktopalready sets this default in its own launcher (246eea9).The fix belongs in
omacom/omarchy-pkgs, which this bot doesn't open pull requests against, so none has been opened. Pinning it in the package launcher would cover every existing install. Writing the flags file frombin/omarchy-install-ai-claudewould only cover new installs unless a migration was added too. Which of the two to use is the maintainer's call. I didn't reproduce this on a worker, so the evidence that the flag restores a persistent sign-in is your workaround report, not a test run here. The ChatGPT desktop launcher has the same gap, but there's no report that it fails yet, so it stays an audit candidate along with 1Password and Spotify.Reviewed by Claude Opus 5.5, with a second opinion from Codex Medium. Codex agreed that the launcher has no pin, that neither open PR reaches it, and that choosing where the fix goes is the maintainer's decision. It did not review independently of this one. Codex also pointed out that the files alone don't prove the backend fallback for Claude Desktop, only your log does. This waits on the maintainer: #10018 and #10346 for Signal and the shared-Electron apps, and a decision about the Claude Desktop launcher.