[Bug]: Desktop Client does not automatically synchronize anymore

[NicolasGoeddel]

⚠️ 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

For a few weeks now, I have noticed that the Nextcloud Desktop Client no longer automatically synchronizes file changes on the server side. You always have to pause and restart synchronization for it to happen. Or a file has to be changed locally to trigger it and start syncing again.

I have observed this behavior on two Ubuntu computers. On Ubuntu 24.04 and 25.04.

Here are my settings:

Steps to reproduce

1. Change a file on the server, either through the webinterface or using another client.
2. Resume your PC from suspend and wait.
3. Even after an hour the changes were still not synchronized.
4. Then change the same file locally.
5. A few seconds later the client shows a notification about a file conflict.

Expected behavior

After starting up the PC from suspend the Nextcloud Desktop client should synchronize changed files from the server in the configured 30 seconds interval.

Which files are affected by this bug

Any file

Operating system

Linux

Which version of the operating system you are running.

Ubuntu Gnome 24.04 or 25.04

Package

Official PPA

Nextcloud Server version

Nextcloud Hub 25 Autumn (32.0.1)

Nextcloud Desktop Client version

4.0.1daily

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

Updated to a major version (ex. 3.16.3 to 3.17.0)

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

It's empty

Additional info

The "AppAPI-Bereitstellungs-Daemon" is not configured properly on server side. But I don't think this is the issue.