mimick could not store the API key in your desktop keyring.

[farangkao]

installed via flatpak
flatpak install flathub dev.nicx.mimick
(during install got asked if user or system, tried both versions)

App launches fine. But got error: mimick could not store the API key in your desktop keyring. when trying to add my api key
OS: Omarchy (Arch based) with Hyprland.

tried directly from the console to see the error log ,these warning/errors were reported:

[2026-07-15 15:35:46.830911 +02:00] WARN  [mimick::api_client::albums] Cannot  
[2026-07-15 15:36:15.322011 +02:00] ERROR [mimick::config] Failed to save API key via oo7 keyring:   File(Portal(PortalNotFound(OwnedInterfaceName("org.freedesktop.portal.Secret")))) src/config.rs:476  

Note: testing the connection was succesful.

config.redacted.json
privacy-note.txt
retries.redacted.json
status.redacted.json
summary.txt
synced_index.redacted.json

[farangkao]

okay, i could figure it out with the help of AI, here a summary:

API key save fails on Hyprland — PortalNotFound("org.freedesktop.portal.Secret")

Arch Linux, Hyprland (Wayland) — may also be reproducible on Sway and other wlroots compositors

Root cause

Mimick uses the oo7 keyring, which stores credentials via the org.freedesktop.portal.Secret portal. That interface is implemented by gnome-keyring and kwallet, but both ship .portal files with UseIn=gnome / UseIn=kde. On compositors that match neither token (Hyprland, Sway, …), xdg-desktop-portal skips them, so the Secret portal is never exposed → PortalNotFound. It works out-of-the-box on GNOME/KDE for this reason.

This is not a Mimick bug — it's a desktop-side portal wiring gap. It just surfaces most visibly here because the failure is a hard error.

Fix (user side)

Prerequisites: gnome-keyring (or kwallet) and libsecret installed, and the keyring daemon running. (which was true in my case)

Create ~/.config/xdg-desktop-portal/portals.conf (or system-wide /etc/xdg-desktop-portal/portals.conf):

[preferred]
default=hyprland;gtk          # use your compositor's backend + gtk for the rest
org.freedesktop.impl.portal.Secret=gnome-keyring   # or kwallet, if you use KWallet

Then:

systemctl --user restart xdg-desktop-portal

Suggestion for Mimick (from my friendly AI)

When oo7 returns PortalNotFound, fall back to a non-portal Secret Service backend (the standard org.freedesktop.secrets D-Bus API) or offer an unencrypted fallback, instead of failing hard. Even better: catch this error and point users at the portal config, since the current message is opaque to most users.

[denk-mal]

I have the same error on a standard XFCE (MX Linux) using the xfwm4 compositor and the user side workaround is not working.
The gnome-keyring-daemon, xdg-desktop-portal and xdg-desktop-portal-gtk are up and running.

[farangkao]

I have the same error on a standard XFCE (MX Linux) using the xfwm4 compositor and the user side workaround is not working. The gnome-keyring-daemon, xdg-desktop-portal and xdg-desktop-portal-gtk are up and running.

Did you adjust correctly your config?
Mine is specific for Hyprland

If unsure ask Ai to evaluate the right config for your system

[denk-mal]

I ask an AI and got three answers; The first two that were nearly similar to your didn't work out but the third one gives me the right solution.

I had to install xdg-desktop-portal-xapp also and extent the xfce-portals.conf file in /usr/share/xdg-desktop-portal/ from

[preferred]
default=gtk;

to

[preferred]
default=xapp;gtk;

And on my system I also must remove the ~/.config/xdg-desktop-portal/portals.conf and the /etc/xdg-desktop-portal/portals.conf) files to get it working. YMMV

[nicx17]

Sorry I've been busy with college stuff... Is this issue resolved or needs fix?

[farangkao]

@nicx17 : the issue is not solved 100% ,see "Suggestion for Mimick (from my friendly AI)" in my original post.
However there is a workaround, as described and discussed between me and denk-mal.
It's not strictly a bug of mimick, but something you might want to document and improve the error handling on, if you have time.

[denk-mal]

@nicx17 : I also see this not as fixed because there is a workaround but I have needed a different one as farangkao and furtermore for a non-technical user it is very hard to find the reason and even harder to get the correct working workaround.