Re: nextcloud client no longer working

Re: nextcloud client no longer working

[yopito]

[-- Attachment #1: Type: text/plain, Size: 179 bytes --]

New comment by yopito on void-packages repository

https://github.com/void-linux/void-packages/issues/26774#issuecomment-738625025

Comment:
nope: libsecret is a GNOME-only stuff

Re: nextcloud client no longer working

[yopito]

[-- Attachment #1: Type: text/plain, Size: 324 bytes --]

New comment by yopito on void-packages repository

https://github.com/void-linux/void-packages/issues/26774#issuecomment-779064993

Comment:
Added a subpackage `nextcloud-client-kwallet` in PR #28674.

Purpose: make nextcloud-client uses kwallet as credential backend storage while not using KDE as Desktop Environment.

Re: nextcloud client no longer working

[yopito]

[-- Attachment #1: Type: text/plain, Size: 601 bytes --]

New comment by yopito on void-packages repository

https://github.com/void-linux/void-packages/issues/26774#issuecomment-778671045

Comment:
thanks for you detailed answer.

I don't feel confident to patch qtkeychain the way you propose. it's too intrusive for me, at least because it's changing a lot the way it's working compared to upstream. It will also make even more difficult to discuss with upstream in case of trouble.

Instead, I prefer to make a wrapper via a dedicated package to help people using nextcloud with kwallet as credential storage, while not wihin KDE Desktop Environment.

Re: nextcloud client no longer working

[gt7-void]

[-- Attachment #1: Type: text/plain, Size: 1919 bytes --]

New comment by gt7-void on void-packages repository

https://github.com/void-linux/void-packages/issues/26774#issuecomment-763043678

Comment:
Since `LibSecretKeyring::isAvailable()` does *not* check if secret service is available, only that the library is installed (it seems the library doesn't provide any way to check availability of the service), the only reasonable fix seems to be changing the order of the tests as in:
```diff
     default:
+        if (isKwallet5Available()) {
+            return Backend_Kwallet5;
+        }
         if (LibSecretKeyring::isAvailable()) {
             return Backend_LibSecretKeyring;
         }
         if (GnomeKeyring::isAvailable()) {
             return Backend_GnomeKeyring;
         }
-        if (isKwallet5Available()) {
-            return Backend_Kwallet5;
-        }
```
Note that setting `DESKTOP_SESSION=kde`, etc. might have some undesirable side-effects, so this patch should be preferred. 

Otherwise, there's no way to use any other backend than libsecret if `libsecret` is installed [1] , so you need to install a secret service provider. I could find two in void:
- `gnome-keyring`
- `keepassxc` (depends on #28020 to work)

Meanwhile I was using `kwallet` only because `qtkeychain-qt5` did not work with `gnome-keyring before. With the current `qtkeychain-qt5` now `gnome-keyring` works out of the box for me (just install it, no configuration necessary as long as `libsecret` is installed). The alternative `keepassxc` seems to work, but I didn't like it (cf https://avaldes.co/2020/01/28/secret-service-keepassxc.html for a guide).

For `pass` users, there's this: https://pypi.org/project/pass-secret-service/ (source here: https://github.com/mdellweg/pass_secret_service) but I don't know if it works.

[1] for me `libsecret` is an (indirect) dependency of `mediainfo` (surprising, as I only use the command line tool).