Libsecret + gnome-keyring + qykeychain broken (was nextcloudclient fails to work with gnome-keyring)
Hello again. I reproduced the issue once again: I performed a fresh install of -current and installed Gnome. Starting Gnome via GDM brings up all the services necessary for storing secrets (dbus and gnome-keyring) out-of-the-box. Nextcloud Client is still incapable of leveraging libsecret or Gnome Keyring for storing secrets in a keyring in this configuration. My conclussion, unless somebody brings an alternative, is that either Libsecret, Gnome Keychain, qtkeychain or Nextcloud Client are broken. If it is one of the first three, it means such port is broken since it cannot perform the primary function expected from it. Since interest in having this working is low I am staying with my workaround of using kwalletd5 instead. If anybody is willing to debug this problem further I am willing to provide more information. Rubén Llorente wrote: > 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. > -- OpenPGP Key Fingerprint: 543F EB89 7FDE 8E33 AFF7 E794 E4AB 4807 58F7 6C76
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 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
nextcloudclient fails to work with gnome-keyring
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
