Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Bug]: Client keeps resetting folder sync settings and syncs _everything_ instead #6229

Closed
5 of 8 tasks
moedn opened this issue Nov 17, 2023 · 5 comments
Closed
5 of 8 tasks

Comments

@moedn
Copy link

moedn commented Nov 17, 2023

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

Bug description

My desktop sync client is set up for multiple accounts and selective sync settings and has been running for years without any issues. Since about a month these selective sync settings seem to reset themselves and since today this is happening for two accounts, on two different nextcloud server versions (which haven't changed lately, so I assume it's on the client side).

Example: I have a large folder on the server side with let's say 30 subfolders and only want to sync 4 of them. When I hit "apply" the connection is established, folders are synced, all good. Then, silently, the client starts syncing all other subfolders as well although they don't appear as selected in the sync client's settings. When I restart the client, all folders are selected. Resetting the configuration (deleting all data locally, deleting the folder connection, adding the folder connection anew, downloading the data via the client) doesn't change the behavior.

This is especially annoying since the sync fills up my disc until it is full and the sync stops – and this happened repeatedly on mobile data and got a little pricy.

Steps to reproduce

  1. create a selective folder connection (= only sync selected subfolders)
  2. sync, everything looks fine
  3. at some point all other subfolders are synced as well…
  4. and the sync settings (= selection which folders to sync) have changed to all

Expected behavior

sync only the selected subfolders

Which files are affected by this bug

all

Operating system

Linux

Which version of the operating system you are running.

Fedora Linux 38

Package

Distro package manager

Nextcloud Server version

27.1.2

Nextcloud Desktop Client version

3.10.0

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

Updated to a major version (ex. 3.3.6 to 3.4.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

asked the admin for an export

Additional info

happy to help with local logs; please just tell me where I can export them :)

@moedn
Copy link
Author

moedn commented Nov 17, 2023

update: I tried a workaround, adding only the the subfolders I want to sync completely as a connection, but the client started syncing the whole cloud instead. So it's seemingly not only resetting the folder sync settings but also ignoring them all along

just uninstalled the client and there's 2 files I can't delete, in the folder where synced subfolders are:

image

when I delete them, they're instantly regenerated

hope that helps

EDIT: now deletion worked, but reinstalling doesn't change the behavior. however, the uninstall didn't seem to be complete since the client remembered all my accounts and folder sync settings

the sync client is by that currently unusable for me

@phil8900
Copy link

We are seeing the same behaviour with Nextcloud Server 27.1.3 in combination with Nextloud Client 3.10.1.

@moedn
Copy link
Author

moedn commented Nov 27, 2023

I deleted the locally created folders I didn't want to sync and the client (naturally, but didn't come to my mind) deleted the folders on the server… so looks like the folder sync settings are just completely bypassed

@moedn
Copy link
Author

moedn commented Dec 11, 2023

I just found this comment in the commits for #6143 that has been fixed for v3.10.2

I might give it a try next week or so and see if the update solves this issue (for me at least)

@moedn
Copy link
Author

moedn commented Jan 3, 2024

have v3.11.0 installed now on a fresh system install (Fedora 39) – seems to work fine now ✨

@moedn moedn closed this as completed Jan 3, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants