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

[Qt6][Windows][Bug]: Some kind of timeout when starting to sync (file download fails) #6768

Closed
4 of 8 tasks
Tracked by #6774
allexzander opened this issue May 18, 2024 · 3 comments · Fixed by #6987
Closed
4 of 8 tasks
Tracked by #6774

Comments

@allexzander
Copy link
Contributor

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

Bug description

Set up a new folder connection to the server and start syncing files. More than 50% of the time, some files will fail to sync with an error displayed as a timeout of network connection. This happens with and without virtual files (you need to try to download a file with VFS in order for this to happen).

Steps to reproduce

  1. Install a desktop client build built with Qt6
  2. Setup a new folder connection and start syncing files
  3. Observe the issue

Expected behavior

Syncing works as expected similar to how it works with Qt5 build.

Which files are affected by this bug

all

Operating system

Windows

Which version of the operating system you are running.

All Windows

Package

Other

Nextcloud Server version

all

Nextcloud Desktop Client version

3.13.50

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

Fresh desktop client install

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

No response

@allexzander
Copy link
Contributor Author

@mgallien

@mgallien
Copy link
Collaborator

@tobiasKaminsky blocking bug for any release based on master branch

@mgallien
Copy link
Collaborator

Closed by #6987

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants