Default keyring assumed to be named 'login.keyring'?
Hi all,
I'm not sure if this is the right place to post this. I initially hit this issue when installing the Fractal development version (See this issue), and it caused the application not to start due to an error with the ''Secret Service''. Digging through the logs we found the culprit to be the following line in the journal:
xdg-desktop-por[4454]: Backend call failed: Collection login doesn't exist
So we concluded that it was searching for the wrong keyring. My default keyring is named Default_keyring.keyring
. I created a symlink login.keyring
that points to the other and then it worked.
However now I realize that for some reason it has started making 65535 copies of the symlink, all named login.keyring.temp-<some-number>
.
Is this a known issue? And can I safely rename my default keyring or will this cause issues with other applications?
Additional information
- Host OS: Manjaro ARM (Pinephone)
- The fractal dev-version isn't using libsecret directly, but via rust bindings generated here