Skip to content

Electron apps other than browsers aren't pinned to gnome-libsecret: migrated Signal profiles become unrecoverable on Hyprland #10005

Open

Description

@johnfire

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

  1. On a machine with a working keyring, use signal-desktop so its DB key is stored under gnome_libsecret.
  2. Copy ~/.config/Signal to an Omarchy/Hyprland machine.
  3. 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.conf

Confirmed: 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

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

  1. matt8poi commented on Sep 9, 2026

    @matt8poi

    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/electronNN reads:

    ~/.config/electronNN-flags.conf    # e.g. electron43-flags.conf
    ~/.config/electron-flags.conf      # fallback, any version
    

    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-desktop is the entire wrapper:

    #!/bin/sh
    exec electron43 /usr/lib/element/app.asar "$@"

    so ~/.config/electron{43,}-flags.conf is the only place the pin can go.

    obsidian is in this class too, and is shipped in install/omarchy-base.packages (depends on electron43, 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-desktop will not start at all. Electron selects basic_text, and Element refuses to run on it:

    System unsupported — Your system has an unsupported keyring, which means the database cannot be opened.

    Repro is just sudo pacman -S element-desktop and launch it. gnome-keyring is running and org.freedesktop.secrets is registered on the session bus, so the keyring itself is fine — Electron never asks for it.

    Same fix: --password-store=gnome-libsecret in ~/.config/electron43-flags.conf. Element then logs Using storage mode 'encrypted' with backend 'gnome_libsecret' and records the choice.

    Implementation trap for whoever fixes this

    /usr/bin/electronNN selects its flags file with elif:

    flags_file="${XDG_CONFIG_HOME:-$HOME/.config}/${name}-flags.conf"
    fallback_file="${XDG_CONFIG_HOME:-$HOME/.config}/electron-flags.conf"
    
    if [[ -f "${flags_file}" ]]; then
        mapfile -t lines < "${flags_file}"
    elif [[ -f "${fallback_file}" ]]; then
        mapfile -t lines < "${fallback_file}"
    fi

    So backfilling the generic electron-flags.conf silently does nothing for anyone who already has a versioned electronNN-flags.conf. The generic file is otherwise the better target: it survives the electron43 → electron44 bump, and shipping it as config/electron-flags.conf would make it reachable via omarchy refresh config, the way chromium-flags.conf already 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.

  2. omarchybot commented on Oct 11, 2026

    @omarchybot
    Collaborator

    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 in bin/omarchy-install-editor-vscode. The mechanism you describe is real, and both parts of this report already have an open fix:

    • Signal: Pin Signal to gnome-libsecret like the browsers #10018, which closes this issue. It writes --password-store=gnome-libsecret to ~/.config/signal-desktop-flags.conf before the first launch from omarchy-install-service-signal, and adds a migration for existing installs. It was verified on a Hyprland worker with Signal 8.26.0. A gnome_libsecret profile failed to decrypt without the pin, opened after the migration, and failed again once the pin was removed.
    • Shared-Electron apps from the comment above: Pin Electron password store to gnome-libsecret #10346. It ships config/electron-flags.conf and pins electron-flags.conf along with any versioned electronNN-flags.conf that would shadow it. /usr/bin/obsidian launches through electron43, 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.

  3. e2goon commented on Oct 18, 2026

    @e2goon

    Claude Desktop hits this too, and neither open fix reaches it.

    claude-desktop 2.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.conf and adds --ozone-platform=wayland, but no --password-store. On Hyprland it falls back to basic_text, so the sign-in is never saved and I have to log in again after every restart. From ~/.config/Claude/logs/main.log:

    [safeStorage] isEncryptionAvailable=false on linux at startup (backend=basic_text) — session will not persist; app secrets fall back to plaintext
    [oauth-v2] safeStorage not available, tokens will not persist
    

    Local State has "os_crypt":{"portal":{"prev_desktop":"Hyprland","prev_init_success":false}}, the same failure migrations/1784508556.sh describes for browsers.

    #10018 and #10346 don't cover it, since it reads neither signal-desktop-flags.conf nor electron-flags.conf. omacom/omarchy-pkgs#274 had a launcher that pinned gnome-libsecret, but it was closed in favor of omacom/omarchy-pkgs#348, and the launcher shipped now doesn't have the pin.

    Workaround:

    echo '--password-store=gnome-libsecret' >> ~/.config/claude-desktop-flags.conf
    

    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.

  4. omarchybot commented on Oct 18, 2026

    @omarchybot
    Collaborator

    Checked the Claude Desktop report against omacom/omarchy-pkgs master. The launcher it ships at /usr/bin/claude-desktop (pkgbuilds/claude-desktop/claude-desktop-launcher.sh) reads ~/.config/claude-desktop-flags.conf and adds --ozone-platform=wayland on Wayland, but never passes --password-store. So unless the user has added the flag, Electron picks its own backend, which fits the basic_text line in your log. Neither open fix reaches it: #10018 writes signal-desktop-flags.conf, and #10346 covers Arch's shared electronNN wrappers, which this bundled Electron doesn't go through.

    omarchy-pkgs#274 did pin gnome-libsecret in 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-desktop already 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 from bin/omarchy-install-ai-claude would 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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions