Hey, > Well I wondering if it is even requesting dbus. > > For instance looking at the log with “ dbus-monitor > "path=/org/freedesktop/secrets" ” I can see other applications requesting > pwd from Seahorse (ie. polari irc client or Chromium), but launching > nextcloud-desktop doesn't trigger any similar "method call".
well qtkeychain tries to detect once the backend and falls back to other if the backend does not answer. So you may have success if you first request a password via seahorse and than afterwards start nextcloud-client? > Maybe the configure part in the build is failing to activate libsecret > feature (just a bold guess as I've not look at the source yet)? well the configure part in the build is quite simple: HAVE_LIBSECRET=1 if the lib is found and you see from the builts that this flag is set: https://buildd.debian.org/status/fetch.php? pkg=qtkeychain&arch=arm64&ver=0.9.1-1&stamp=1549301996&raw=0 Here the entry points to the source. Maybe with more debug messages you find out what is going on there: https://sources.debian.org/src/qtkeychain/0.9.0-2/keychain_unix.cpp/#L135 https://sources.debian.org/src/qtkeychain/0.9.0-2/libsecret.cpp/#L196 hefee
signature.asc
Description: This is a digitally signed message part.
