STEPS TO REPRODUCE 1. Launch Nextcloud Sync Client (Flatpak) OBSERVED RESULT Nextcloud Sync Client asks for credentials (i.e. to open the browser and grant acces via the nextcloud web interface) EXPECTED RESULT Nextcloud Sync Client can access the already stored credentials and hence does not ask to grant credentials again. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Fedora 40, Kernel 6.8.9-300.fc40.x86_64 KDE Plasma Version: 6.0.4 KDE Frameworks Version: 6.2.0 Qt Version: 6.7.0 Nextcloud Sync Client: 3.12.3 (flatpak) ADDITIONAL INFORMATION Potentially helpful entry from the Nextcloud Sync Client Logfiles: 2024-05-16 11:18:25:479 [ info nextcloud.sync.credentials.keychainchunk /run/build/nextcloud-client/src/libsync/creds/keychainchunk.cpp:346 ]: Backend unavailable (yet?) Retrying in a few seconds. "user interaction failed" It has been working until today. Nextcloud client sync hasn't been updated prior to the problems started occuring. I didn't change any flatpak permissions etc. Regarding this and the beforementioned error log entry i think the kde wallet system is to blame.
Created attachment 169556 [details] DNF updates that broke it I have also a second system running the same OS an versions stated above (Fedora 40, Plasma 6, wayland, Nextcloud via flatpak) and booted it today: at first there were no problems, the nextcloud sync client did behave as it should. then i updated my system and the problem started to begin. so i suppose one of the attached updates is the culprit.
Possibly related to the new XDG Secrets Portal implementation at https://invent.kde.org/frameworks/kwallet/-/merge_requests/67
(In reply to dreadlock.septic926 from comment #2) > Possibly related to the new XDG Secrets Portal implementation at > https://invent.kde.org/frameworks/kwallet/-/merge_requests/67 See bug 466197 and the comment thread at https://invent.kde.org/frameworks/kwallet/-/merge_requests/67#note_944107 for details
Did you try reinstalling the Flatpak and removing its existing config files and other data?
(In reply to Daniel Rusek from comment #4) > Did you try reinstalling the Flatpak and removing its existing config files > and other data? Yes, I have tried that for both the Bitwarden and the Standard Notes flatpaks, but this did not resolve the issue. Successful workarounds for the issue include switching to the Bitwarden and Standard Notes AppImages, or switching the desktop environment to GNOME Shell 46.1, or rolling back KDE Frameworks to version 6.1.0. It is the combination of KDE Wallet 6.2.0 and the Bitwarden and Standard Notes flatpaks that cause the issue on my end.
(In reply to Daniel Rusek from comment #4) > Did you try reinstalling the Flatpak and removing its existing config files > and other data? yes, i uninstalled nextcloud via the --delete-data flag and subsequently reinstalled it. at some point in the last days an update for the nextcloud client was distributed, 3.12.3-1. It helped _a little_: now it is at least possible to _reliably and repeatably_ create a token with the kdewallet subsystem _enabled_, which wasn't the case before that update (before that update i _somehow_ managed it to get working by enabling/disabling/logging in or out/rebooting/ etc. and at some point it worked, but i still dont know when or how). it still doesn't work at all with the kdewallet subsystem _disabled_.
Just to clarify, my issue and the issues reported at https://invent.kde.org/frameworks/kwallet/-/merge_requests/67#note_944107 are all with KWallet enabled. I'll split these issues to a new bug report if necessary.
*** This bug has been marked as a duplicate of bug 487348 ***