Re: nextcloudclient fails to work with gnome-keyring

I have reproduced the issue in Fluxbox.

~.xession:

/usr/local/bin/startfluxbox


~.fluxbox/startup

if [ -z "$DBUS_SESSION_BUS_ADDRESS" ]; then
eval $(dbus-launch --sh-syntax --exit-with-session)
fi

exec fluxbox


Under a similar configuration in Linux, Nextcloud calls
a prompt for creating a password database on first launch,
and stores the credentials in a keyring. In OpenBSD this
happens not.

Some worrying logs from Nextcloud:

2021-09-25 00:52:25:016 [ info nextcloud.sync.credentials.webflow ]: Get QNAM
2021-09-25 00:52:25:667 [ info nextcloud.sync.credentials.webflow ]: Fetch from keychain!
2021-09-25 00:52:25:985 [ info nextcloud.sync.credentials.keychainchunk ]: Backend unavailable (yet?) Retrying in a few seconds. "Unknown error"
2021-09-25 00:52:36:312 [ warning nextcloud.sync.credentials.keychainchunk ]: Unable to read "someuser_clientCertificatePEM:https://somedomain.invalid/:0" chunk "0" "Unknown error"
2021-09-25 00:52:36:313 [ info nextcloud.sync.credentials.keychainchunk ]: Backend unavailable (yet?) Retrying in a few seconds. "Unknown error"
2021-09-25 00:52:46:491 [ warning nextcloud.sync.credentials.keychainchunk ]: Unable to read "someuser_clientKeyPEM:https://somedomain.invalid/:0" chunk "0" "Unknown error"
2021-09-25 00:52:46:491 [ warning nextcloud.sync.credentials.webflow ]: Unable to read client key "Unknown error"
2021-09-25 00:52:46:492 [ info nextcloud.sync.credentials.keychainchunk ]: Backend unavailable (yet?) Retrying in a few seconds. "Unknown error"
2021-09-25 00:52:56:186 [ warning nextcloud.sync.credentials.keychainchunk ]: Unable to read "someuser_clientCaCertificatePEM0:https://somedomain.invalid/:0" chunk "0" "Unknown error"

"Unknown Error" is returned by qtkeychain when unable to operate its
backend.

Either there is a problem with libsecret or the PEBKAC level is
astronomical at this point.

Rubén Llorente <porting@use.startmail.com> wrote:
> Hello there!
>
> I have been testing some machine for deployment as a workstation. I have set up XFCE4 as a desktop environment (which is launched by my .xsession file). I have also set nextcloudclient and installed gnome-keyring-daemon.
>
> I have found that Nextcloud Client is unable to leverage gnome-keyring in order to save credentials securely. Nextcloud Client always complains because the secrets agent cannot be used because of an "Unknown Error".
>
> Things I have tried in order to properly launch gnome-keyring-daemon include:
>
> Using an .xsession script such as:
>
>
> . $HOME/.profile
> eval $(/usr/local/bin/gnome-keyring-daemon --start )
> export GNOME_KEYRING_CONTROL GNOME_KEYRING_PID GPG_AGENT_INFO SSH_AUTH_SOCK
> /usr/local/bin/startxfce4
>
> Also, I have tried using the XFCE4 desktop configuration tool, enabling Gnome Services on startup in the Advanced tab.
>
> Essentially, I can get the keyring started, but nextcloud, or qtkeychain, or whatever backend is suppose to talk to gnome-keyring fails to find it.
>
> As a workarround I am using Kwalletd5 for the time being, which works.
>
> If anybody has any guide or instructions to set up gnome-keyring with nextcloudclient, or ideas to get such setup working, I am eager to read your ideas.
>
> The working environment is OpenBSD 6.9 -RELEASE amd64.
>

--
OpenPGP Key Fingerprint:
543F EB89 7FDE 8E33 AFF7 E794 E4AB 4807 58F7 6C76