Hey kaliko, > Can't confirm Thomas fix.
thanks for testing. > I did force libsecret as a build dependency on nextcloud-desktop, but it did > not solve the issue. > > Anyway nextcloud-desktop already fetches libsecret with the current build > (nextcloud-desktop build-dep on qt5keychain-dev → libqt5keychain1 → > libsecret-1-0) > > I also tried building nextcloud-desktop with a Build-dep on libsecret-1-dev > as mentioned by Thomas in #909588 [0] > > In both case I patched d/control and built from a clean chroot (pbuilder). > > @Thomas, How did you build your client when you managed to fix this issue ? > You probably fetch something else or setup a different build env when you > did. My best guess that the root of the issue lies in qtkeychain. I saw that there is a new qtkeychain 0.9.1 with a quite promising line in Changelog: https://github.com/frankosterfeld/qtkeychain/blob/master/ChangeLog#L6 "Secret: Don't match the schema name #114 " So build qtkeychain 0.9.1 and give that a try. hefee
signature.asc
Description: This is a digitally signed message part.
