https://bugs.kde.org/show_bug.cgi?id=479834
--- Comment #10 from b...@mogwai.be --- (In reply to Linus Kardell from comment #9) > Looks like that commit > (https://github.com/flathub/org.kde.kasts/commit/ > e8901209ab3e50eee090ad9d2c506fb80db57f1e), undid the change from > https://github.com/flathub/org.kde.kasts/pull/7/commits/ > 6c12efef965cdb0cf17fccd15f5b42291c845fbb that worked around the issue at > https://bugs.kde.org/show_bug.cgi?id=451836. Thanks for reminding me of my own workarounds from the past. :facepalm: I had forgotten the underlying reason for the -Dgcrypt=false. Having said that, I had to remove it from the flatpak manifest, because that option simply doesn't exist anymore with libsecret > 0.21. So it was necessary for the flatpak to build. The puzzling thing is that it works perfectly fine for me with multiple keychain backends, while in the past it would consistently fail without -Dgcrypt=false. It would be nice to have a problem which is reproducible everywhere. Going through the libsecret documentation, I think I've found the replacement option. So let me try to set up a PR with those changes. Would you be ok testing the automatic build generated by that PR to see if it helps? -- You are receiving this mail because: You are watching all bug changes.
