[Bug]: Need to reauthenticate at each client launch

[canoine]

⚠️ Before submitting, please verify the following: ⚠️

• This is a bug, not a question or a configuration issue.
• This issue is not already reported on Github (I've searched it).
• Nextcloud Server and Desktop Client are up to date. See Server Maintenance and Release Schedule and Desktop Releases for supported versions.
• I agree to follow Nextcloud's Code of Conduct

Bug description

Each time I launch the nextcloud desktop client, all my accounts are disconnected, and I need to re-authenticate inside the application web interface.

And each new authentication is a new session :

As I already said in #5466, all worked well under a 6.1.27 kernel. The problem appears when I reboot on a newly compiled 6.1.28 kernel on the stations. Today, I run a 6.1.31 kernel, with the same bug.

Steps to reproduce

1. Launch the desktop client
2. Authenticate
3. Stop the client
4. Launch the desktop client
5. Authenticate
6. Stop the client
   ...

Expected behavior

The credentials should be kept.

Which files are affected by this bug

N/A

Operating system

Linux

Which version of the operating system you are running.

Gentoo stable and up-to-date

Package

Distro package manager

Nextcloud Server version

25.0.3, 25.0.4, 25.0.6, 26.0.0, 26.0.1. On two different servers (Gentoo and Debian 8).

Nextcloud Desktop Client version

3.7.3 and 3.8.0. On two different stations (Gentoo both).

Is this bug present after an update or on a fresh install?

Updated from a minor version (ex. 3.4.2 to 3.4.4)

Are you using the Nextcloud Server Encryption module?

Encryption is Disabled

Are you using an external user-backend?

• Default internal user-backend
• LDAP/ Active Directory
• SSO - SAML
• Other

Nextcloud Server logs

No response

Additional info

If you really want my logs and debug archives, I need to anonymize all the names (domain, files, and so on)...

[Flowdalic]

Same here with nextcloud-desktop 3.9.1. Any suggestions on how to debug and approach this issue would be appreciated.

[Flowdalic]

See also

• Client needs to manually login after every start #2573 (comment)
• https://bugs.gentoo.org/912844

[canoine]

That's it ! You made my day @Flowdalic . 😃
Adding the "keyring" USE flag for dev-libs/qtkeychain solved the issue.

[Gahia123]

That's it ! You made my day @Flowdalic . 😃 Adding the "keyring" USE flag for dev-libs/qtkeychain solved the issue.

Do you mean add this flag on the client or server side? I've added it to the client side and the problem persist. What could be the cause? I'm using sway desktop environment.

[canoine]

Hello @Gahia123,
On the client side, on a Xorg/GTK DE. So Qt is needed by the desktop client only. I don't need any DE on my servers.

[Dominique-M]

This happens to me under Ubuntu 24.04 with Nextcloud-3.14.0-x86_64.AppImage. (I have no such problem with 3.13.3.) I tried simply connecting and also connecting as an application. In both cases 3.14 asks authentication again at the next launch.

[raider-com]

#5831 (comment)
Can second this.
Prior to this, never had this happen between client application upgrades.
With 3.14.0 app image, happens every time on 3 different PCs that got that upgrade

[gvoigtlaender]

Same here with Debian Trixie and 3.14.0. Going back to 3.13.4 works fine

[DLeich]

Adding my +1 on the experience. Upgrade to 3.14.0 triggered this behavior. Happening on all three of my Ubuntu 24.04 systems.