We are aware of the issue with the badge emails resending to everyone, we apologise for the inconvenience - learn more here.
Linux
3 Topics
Can't un-exclude directories with `dropbox.py exclude remove <directory>` on Ubuntu 20.04.2
I have a Linux machine (running Ubuntu 20.04.2 LTS, "Focal Fossa") upon which I am running a "headless" Dropbox daemon as per here: https://www.dropbox.com/install-linux The Dropbox daemon is up to date: ``` $ dropbox.py version Dropbox daemon version: 125.4.3474 Dropbox command-line interface version: 2020.03.04 ``` This machine is truly "headless", so I am doing everything on the command line. Installation of the daemon and initial sync seemed to work fine, though autostart isn't working for me. I've found that I can exclude directories with `dropbox.py exclude add <directory>` just fine. When I run that command for a directory in my Dropbox, the directory briefly appears in the list output from `dropbox.py exclude`. However, once the directory is actually deleted from the local Dropbox directory, it disappears from the list too. For example, I do have a bunch of directories excluded, and they are not present in the local Dropbox directory. However, the tool incorrectly reports no excluded directories: ``` $ dropbox.py exclude No directories are being ignored. ``` This is fine, if a bit weird, but the problem is that I can't add excluded directories back (un-exclude them?) with `dropbox.py exclude remove <directory>`. That command outputs nothing and has no effect. Why not? How can I get this to work? It seems totally broken right now.7.6KViews10likes43Comments
Dropbox says there's not enough free space on Ubuntu but the cache folder keeps filling it up
My dropbox folder is located in a 1TB HDD. My dropbox folder is aprox 487ΜΒ and nothing else is located in this HDD. The chase foldes is 442GB and i am getting a red Dropbox icon with "can't sync not enough free space) When i delete the chase, the next day is full again. Everything was ok for the last 2 years until few days ago when sudenly this problem came up. What is the solution? I have Ubuntu 16.04.6 LTS.Solved2.5KViews1like6Comments