-
Notifications
You must be signed in to change notification settings - Fork 816
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
MacOS Desktop Client 4.1 freezes immediately after startup #4187
Comments
Same issue here on Linux. |
I observed that bug as well. I did a bit more debugging and can report the following. I am almost sure that it is related to the client and has nothing todo with the server. I had my client connected to a server of 21.0.1 server and a 23.0.0. server. I have files which look totally normal and have already been on nextcloud, and lead to the crash once I moved them. I managed to reproduce now a case which leads on my client always to a crash.
Resolving it:
I originally also tried to manually delete the local caches
To me it looked like it is not needed or helping anything to delete them. |
Have the same problem. Since a few days. |
This bug report did not receive an update in the last 4 weeks. Please take a look again and update the issue with new details, otherwise the issue will be automatically closed in 2 weeks. Thank you! |
This bug report is getting automatically closed due to no answer since the issue has been staled. Thank you! |
Is this the same as #4077? |
MacOS Desktop Client 4.1 freezes immediately after startup.
This happens on Catalina and Monterey. My Nextcloud Server is running 23.0.
I did not find anything useful from the serverlogs, the client is showing me a couple of files that could not be synced because they have "white space at the end of filename" (just before freezing), which is not even true, i checked all the files the client mentioned none had actually a white space at the end.
On server side i get a very unspecific "sabre/dav/Exception: Unkonw error while seeking content"
The text was updated successfully, but these errors were encountered: