-
Notifications
You must be signed in to change notification settings - Fork 903
Description
β οΈ 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
After moving new files to upload into a folder the following happens:
File name changed with the post-fix: "-chunking-1611316522-4-0"
and the file size is around a quarter of it's original size.
Started the video and confirmed just the first part of the video is left and the other parts gone.
So the client renamed and destroyed my file.
My CPU was under heavy load - but that's regularly the case and never caused issues before.
Steps to reproduce
Nextcloud Client was running in the background and the destination of my files where the sync folder.
I copied 9 MP4 files all between 350 and 450 MB file size into a folder from my SSD to my HDD using nautilus.
I confirmed the file transfer was successful and deleted the content on my SSD.
I refresh the folder on the HDD...
I see one file (4th from 9) has a changed file name with the post-fix: "-chunking-1611316522-4-0"
and the file size is around a quarter of it's original size. Started the video and confirmed just the first part of the video is left and the other parts just gone.
Using arch linux with flatpak nextcloud client version 4.0.4 with nextcloud server version 31.0.10
Expected behavior
Use some hidden tmp folder which get excluded from sync which only use case is for handling chunks instead of messing with the original file somehow. Since it already was good to go as it was and just needed to be uploaded.
Which files are affected by this bug
video.mp4
Operating system
Linux
Which version of the operating system you are running.
Arch Linux
Package
Community FlatPak
Nextcloud Server version
31.0.10
Nextcloud Desktop Client version
4.0.4
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
I just checked the logs of today ... empty
all worked file πAdditional info
No response