desktop
desktop copied to clipboard
nextcloud
[Bug] - Desktop client causes explorer to hang if network share is inaccessible
Expected behavior
Nextcloud Desktop sync client should just mark the folder sync as error if the network share is not reachable at the moment.
Actual behavior
tldr: Nextcloud Desktop sync client causes explorer.exe and related processes to hang or have a huge delay in response.
I got 3 Folder Syncs configured in my desktop sync client. One of those was a Samba network share on an Ubuntu server. Last week I retired that server. Naturally, the share wasn't available anymore after that. This caused the Nextcloud client to behave weirdly. When it was started during after logging into Windows or via Start menu, it almost never got to a responsive state. Neither right nor left click worked on the icon in the taskbar to change the settings. Sometimes (after right-clicking and waiting for 10-15 minutes), I could select settings. The settings window would open and immediately be unresponsive again. So I was never able to remove or change the folder sync location. Additionally, while Nextcloud was running, Windows Explorer wouldn't open at all or freeze (application is not responding) during copy / pasting and especially while opening the context menu on files inside and outside of Nextcloud sync folders. The start menu was showing similar issues (late response / freezes). As soon as I "killed" the nextcloud.exe process via task manager, my system would work as normal. (In case it's relevant: I tried removing and reinstalling the client with the same result. Sync configuration was kept between installations) In the end, I had to edit nextcloud.cfg manually to change the folder sync to the new path. I can reproduce the issue by switching the server hostname in the nextcloud.cfg between the old (offline) and new server share.
Steps to reproduce
- Have a folder sync configured to a samba network share
- Switch off server
- Reboot client pc
Client configuration
Client version: 3.4.2 Operating system: Windows 10 Pro 21H1 OS language: en-us Installation path of client: default (C:\Program Files\Nextcloud)
Server configuration
Nextcloud version: 22.2.5
Logs
- Client logfile: As I couldn't upload the debug archive as a single file (~34MB in size) I split it into 2: nextcloud_1.zip nextcloud_2.zip
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!
![github-actions[bot] avatar](https://avatars.githubusercontent.com/in/15368?v=4 "Published by a pub.dev verified publisher"){kind=small}
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!
Could someone please at least acknowledge this bug, so it doesn't go stale every 30 days?
This bug report is getting automatically closed due to no answer since the issue has been staled. Thank you!
Same issue for me too. The hanging does not last that long for me (maybe ~30 seconds) but it is still annoying. Also once a folder is loaded in the explorer it does not hang again. Interestingly this issue applies to folders that are actually not synced with Nextcloud like "Desktop" or "Downloads". On an additional note: this issue also arises even if the folder synced over network is set to "Paused".
I am using the latest version 3.5.0. The issue only happened for the last year or so. Hence it must be something that came during that time.
Could someone please at least acknowledge this bug, so it doesn't go stale every 30 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!
Reporting bugs for Nextcloud sure is annoying.
@FlexW: Can you please remove the stale flag from this bug report? We have at least two users with this issue who confirmed.
This bug report is getting automatically closed due to no answer since the issue has been staled. Thank you!
This bug report is getting automatically closed due to no answer since the issue has been staled. Thank you!
The bug remains... please keep it open!
This bug report is getting automatically closed due to no answer since the issue has been staled. Thank you!
This bug report is getting automatically closed due to no answer since the issue has been staled. Thank you!
I have the same issue, Nextcloud client 3.6.0. The symptoms are identical (Nextcloud is almost never responsive, Explorer freezes up, right click hangs even on non-Nextcloud files, and after closing Nextcloud, everything is working again). However, I don't have any inaccessible share, just one, perfectly accessible (at least in the browser) nextcloud drive.
Same problem here on version 3.6.1, after opening the explorer it just freezes for ~15 seconds, after this initial freeze it just behaves normally, even after closing and reopening the explorer. Only after a restart or after waking from sleep the issue comes up again, really annoying. The problems started after switching to virtual file support and persisted since then.
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 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 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 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!
Started getting on 3.9.0 after moving to 27 branch... (and changed dns configuration), so not sure exactly where is the cause, but it's annoying as hell.
