Hey,
If KWallet itself is running but no token is written after you log in, you’re probably hitting the well-known bug introduced in client 3.14: the AppImage sometimes fails to hand its OAuth token to the keyring, so every reboot opens the browser again.(GitHub, Nextcloud community)
What you can try
| Option | Effect |
|---|---|
| Enable auto-unlock | sudo apt install kwallet-pam → log out/in. This unlocks KWallet during login; for some users the token finally sticks.(Arch Linux Forums) |
| Use the Flatpak build | Flatpak 3.16.x stores the token correctly for most people and skips the browser step. https://flathub.org/apps/com.nextcloud.desktopclient.nextcloud |
| Downgrade to 3.13.4 AppImage | Last pre-3.14 build; token storage works reliably. |
After applying one of these, log in once more, reboot, and confirm whether the client finally stays connected.
Let us know which workaround does the trick.