You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When syncing files from the server to the client on Windows, files with a local path slightly smaller than 260 characters (and over 260 characters) crash the application. It appears that the issue is the length of the temporary file path that's created during sync; when that temporary file name is longer than 260 characters, I see this error.
Example:
This file path is 259 characters long: C:/Users/uuuuu/Nextcloud/Redacted/Redacted/Redacted/Redacted/Redacted/Redacted/Redacted/Redacted/Redacted/Redacted/Redacted/Redacted/Redacted/Redacted/Redacted/Redacted/Redacted/Redacted/Redacted/Redacted/Redacted/Redacted/Redacted/Redacted/x__filename__x.pdf
During the sync process, it appears that the filename is prepended with a '.' and appended with a unique string (e.g. '.~47fc').
This results in an error when setting mtime: 2024-10-03 16:35:56:955 [ warning nextcloud.sync.filesystem C:\Users\User\AppData\Local\Temp\windows-26085\client-building\desktop\src\libsync\filesystem.cpp:204 ]: Error setting mtime for "C:/Users/uuuuu/Nextcloud/Redacted/Redacted/Redacted/Redacted/Redacted/Redacted/Redacted/Redacted/Redacted/Redacted/Redacted/Redacted/Redacted/Redacted/Redacted/Redacted/Redacted/Redacted/Redacted/Redacted/Redacted/Redacted/Redacted/Redacted/x__filename__x.pdf.~47fc" failed: rc -1 , errno: 20
Steps to reproduce
Create a network path and file name that is sufficiently long (i.e. when it syncs from the server to the client, the local path is one or two characters shorter than 260 characters)
Sync the folder as virtual files
In Explorer, Select the folder containing the long path name and select "Always keep on this device"
The sync will start but then crash the app when it gets to the file path that is too long.
Expected behavior
I would expect to:
Get a warning that the file name is too long and that it should be made shorter on the server so it can sync to the client.
I should mention that the temporary work around was to change the file paths on the server to be shorter in total length. Once the file paths were sufficiently short, the sync of these files works.
@kmwoley that was already reported in an older issue
closing this one as a duplicate
please provide your feedback on the other one if you can
duplicate: #7258
Bug description
When syncing files from the server to the client on Windows, files with a local path slightly smaller than 260 characters (and over 260 characters) crash the application. It appears that the issue is the length of the temporary file path that's created during sync; when that temporary file name is longer than 260 characters, I see this error.
Example:
This file path is 259 characters long:
C:/Users/uuuuu/Nextcloud/Redacted/Redacted/Redacted/Redacted/Redacted/Redacted/Redacted/Redacted/Redacted/Redacted/Redacted/Redacted/Redacted/Redacted/Redacted/Redacted/Redacted/Redacted/Redacted/Redacted/Redacted/Redacted/Redacted/Redacted/x__filename__x.pdf
During the sync process, it appears that the filename is prepended with a '.' and appended with a unique string (e.g. '.~47fc').
This results in an error when setting mtime:
2024-10-03 16:35:56:955 [ warning nextcloud.sync.filesystem C:\Users\User\AppData\Local\Temp\windows-26085\client-building\desktop\src\libsync\filesystem.cpp:204 ]: Error setting mtime for "C:/Users/uuuuu/Nextcloud/Redacted/Redacted/Redacted/Redacted/Redacted/Redacted/Redacted/Redacted/Redacted/Redacted/Redacted/Redacted/Redacted/Redacted/Redacted/Redacted/Redacted/Redacted/Redacted/Redacted/Redacted/Redacted/Redacted/Redacted/x__filename__x.pdf.~47fc" failed: rc -1 , errno: 20
Steps to reproduce
The sync will start but then crash the app when it gets to the file path that is too long.
Expected behavior
I would expect to:
Which files are affected by this bug
filesystem.cpp
Operating system
Windows
Which version of the operating system you are running.
Windows 11 Home (10.0.22631 Build 22631)
Package
Official Windows MSI
Nextcloud Server version
30.0.0
Nextcloud Desktop Client version
3.14.1
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?
Nextcloud Server logs
No response
Additional info
Redacted client log snippet:
The text was updated successfully, but these errors were encountered: