Dropbox desktop client builds
Download the latest Dropbox beta or stable build.
Download
Windows | Standard Installer | Offline Installer |
Mac OS X | Standard Installer | Offline Installer |
Linux | x86_64 Offline Installer | x86 OfflineInstaller |
Auto-updates: In progress
Same here. On both my win 10 machines, on hovering the Dropbox client icon, I see a message like
"Dropbox 88.4.172
Indexing 1 file...
Uploading 24,856 files (0,0 KB/sec, 6 hrs)...
Downloading 32,504 files..."
And it didn't change for more than 24 hours now. Please help!
My Windows 10 Dropbox clients are also stuck "Syncing..." with no further info.
Version 88.4.172
Same problem here on a headless Ubuntu 18.04 server.. I have 1 TB of dropbox data and since the most recent update the Dropbox client eats 100% CPU (one core) and never finishes syncing no matter what I try.
Hi @Matt F.16,
You can check which files exactly are 'guilty' and investigate further, what's wrong using something like:
dropbox filestatus $(IFS=$'\n';base_path="";for i in `ls -R -1 ~/Dropbox`; do if [[ "$i" =~ ":" ]]; then base_path=`echo "$i" | sed "y/:/\//"`; elif [[ "m$i" != "m" ]]; then echo -n " $base_path$i"; fi; done) | grep -vi "up to date"
Note that "dropbox" command is a script, so processing is relatively slow. You would get "dummy" output if some file name (for directory, even more, all content) contain space! That's Dropbox BUG! Check and see what's the state for particular files. Something like:
ls -l ~/Dropbox/Troublesome/file.ext
Good luck.
I said above that my problems went away after stopping and starting Dropbox, but also after manually finding a conflicted file (ie a file where Dropbox cannot tell which of two versions of that file are correct, so keeps both, but renames one with 'conflict' in its name and added date & time details). Why a conflicted file got created in the first place is a mystery to me, but maybe I edited the file at just the wrong moment as teh dropbox client updated to the latest software version.
The way to find these, if you use Windows, is to open a command window (google for that for your version of Windows if you don't know how to) and then search for files with 'conflict' in their name. I use the command:
dir /b /s "C:\Dropbox\*conflict*"
The asterisks and the double-quote characters are required.
I issue this command every day automatically and can tell if the search works because I have a few innocent test files scattered through my dropbox with 'conflict' in their names... and those should always be found. And, for example, a file that is part of LibreOffice also does, so I always see
C:\Dropbox\PortableApps\PortableApps\LibreOfficePortable\App\libreoffice\share\config\soffice.cfg\modules\scalc\ui\conflictsdialog.ui
as one of the results.
For more info on conflicted files see eg: https://help.dropbox.com/files-folders/share/conflicted-copy
I should add: I understand how conflicted files can occur, when multiple people edit files at the same time etc, but there's only me using my machine, and only one machine using my DB account. The conflicted file I did find was date/time stamped more or less exactly at the time, soon after booting my machine, when I noticed that DB had a problem.
Now my Windows 10 Dropbox client is stuck "uploading 1 file" and "downloading 2 files" even after restarts. Frustrating, since there is seemingly no way to find out which.
This seems to have happend after upgrading to this version.
Same problem on Windows 10. My MacOS is OK.
3 days syncing and no progress.
This was the problem for me:
Several years ago, a Linux client (WSL) had created two files with the same name (differing only in capitalization). After upgrading to 88.4.172, this caused the syncing to never finish.
Hi there!
If you need more help you can view your support options (expected response time for a ticket is 24 hours), or contact us on X or Facebook.
For more info on available support options for your Dropbox plan, see this article.
If you found the answer to your question in this Community thread, please 'like' the post to say thanks and to let us know it was useful!