No Secrets Provider is Installed or Configured

goatcorp / XIVLauncher.Core

Cross-platform version of XIVLauncher, optimized for Steam Deck

GNU General Public License v3.0

134 stars 40 forks source link

No Secrets Provider is Installed or Configured #89

Open noelmiller opened 1 year ago

noelmiller commented 1 year ago

When using flatpak version of XIVLauncher on a KDE based desktop, it complains there is no secrets provider installed, so you cannot save your password to login automatically. Is there some way this can be fixed?

reiichi001 commented 1 year ago

There are 2-3 options:

Install a compatible secrets-provider like gnome-keyring, keepassxc, secret-service (might be disconitnued), or kwallet (only applies to recent versions that added dbus secrets support)
Try enabling dbus support for the XIVLauncher flatpak using Flatseal
Use a native build/community package that doesn't have flatpak restrictions on it.

Usually, the first method is all you really need. Then try 2 or 3.

noelmiller commented 1 year ago

There are 2-3 options:

1. Install a compatible secrets-provider like gnome-keyring, keepassxc, secret-service (might be disconitnued), or kwallet (only applies to recent versions that added dbus secrets support)

2. Try enabling dbus support for the XIVLauncher flatpak using Flatseal

3. Use a native build/community package that doesn't have flatpak restrictions on it.

Usually, the first method is all you really need. Then try 2 or 3.

I have both gnome-keyring and kwallet and it does not detect them. I have tried enabling dbus support and that has not fixed the issue either. My current workaround is using a distrobox with Arch and installing the package from the AUR and that seems to detect my secrets provider.

It seems to me there is something messed up with how XIV Launcher flatpak sees the kwallet secrets provider.

genderneutralnoun commented 7 months ago

I'm having this exact same issue. I have no idea how to implement the workaround noelmiller uses haha.

q9f commented 4 months ago

Also facing this issue on Archlinux, installed xivlauncher-bin from AUR and have gnome-keyring isntalled but it won't store my secrets.

tommadness commented 4 months ago

Also facing this issue on Archlinux, installed xivlauncher-bin from AUR and have gnome-keyring isntalled but it won't store my secrets.

Are you positive the gnome-keyring daemon is running and the keyring has been unlocked for your current session?

blargle-ragequit commented 4 months ago

I sometimes see this on Arch with KDE (but not flatpak) when I try to launch XIV immediately after booting up. I think it's just because kwallet isn't ready yet or something. Just the time it takes me to close the launcher and open it again is usually enough to not see it again.