From: gt7-void <gt7-void@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: nextcloud client no longer working
Date: Tue, 19 Jan 2021 19:41:10 +0100 [thread overview]
Message-ID: <20210119184110.66-0pctIYcerzPIXiE7oQdaCo0XPeeXPcpMe7W9Udec@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-26774@inbox.vuxu.org>
[-- 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).
next prev parent reply other threads:[~2021-01-19 18:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-26774@inbox.vuxu.org>
2020-12-04 7:47 ` yopito
2021-01-19 18:41 ` gt7-void [this message]
2021-02-13 20:06 ` yopito
2021-02-15 8:52 ` yopito
2021-02-24 4:18 ` [ISSUE] [CLOSED] " ericonr
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20210119184110.66-0pctIYcerzPIXiE7oQdaCo0XPeeXPcpMe7W9Udec@z \
--to=gt7-void@users.noreply.github.com \
--cc=ml@inbox.vuxu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).