You might see that the Dropbox Community team have been busy working on some major updates to the Community itself! So, here is some info on what’s changed, what’s staying the same and what you can expect from the Dropbox Community overall.
Forum Discussion
Linux - Unable to change Dropbox directory
I'm using Fedora Workstation 25 with GNOME.
Trying to change the Dropbox directory results in the utterly useless message "Unexpected errors occurred. Your Dropbox is ok!".
Steps to recre...
I was having this same issue. I found a fix in creating a Dropbox folder in my home directory prior to connecting my account. This caused the installer to throw an error about a Dropbox folder already existing that prompted me to either delete the Dropbox folder or select a different location. Eureka! (for me at least...)
Guys solved, and the solution was the easiest and logic.
I expose my situation:
sda1 300GB --> /
sda5 8TB --> /home
As I explained, I wanted to install Dropbox below /home directory, but playing as "root" user, by default, it forced the installation on /root
So I just installed the daemon using the user who owns the home directory I want and it works properly, just remember to add the "user" to the root group.
If you need more details, don't hesitate to ask.
wrote:I was having this same issue. I found a fix in creating a Dropbox folder in my home directory prior to connecting my account. This caused the installer to throw an error about a Dropbox folder already existing that prompted me to either delete the Dropbox folder or select a different location. Eureka! (for me at least...)
This didn't work for me, but I did find a similar solution! I created a "work" dropbox account and set up a fresh installation of dropbox with that account, which places the "work" Dropbox folder in the defaut ~/Dropbox. I then deleted everything in ~/.dropbox* (with rm -rf ~/.dropbox* ), reinstalled dropbox and set it up using my personal account. Now since the folder in ~/Dropbox already contains the dropbox for the work account, I got the prompt that allowed me to either delete the Dropbox folder or select a different location for my personal account. Somehow this worked when simply moving the folder within dropbox wouldn't... I hope this helps somebody! (using Fedora 27 btw)
Dear JaneA,
I have 2 OS on my laptop: Windows 10 and Fedora26. All OS install on SSD.
A HDD drive for share data. It's formatted NTFS. And I have dropbox data on this drive.
Dropbox on Windows 10 is ok as it always.
Dropbox on Fedora failed when I relocate to NTFS drive.
The permission in Fedora is ok for all file of dropbox.
Could you show me the log file location of dropbox, so I can trace the problem.
I think Dropbox team try to protect the log file, so user can't access that.
Thanks in advance.
TuanNV
tuannv0708 wrote:
Could you show me the log file location of dropbox, so I can trace the problem.
I think Dropbox team try to protect the log file, so user can't access that.
As I've stated elsewhere in this thread the log is at ~/.dropbox/logs/ and Dropbox support have told me "you won't be able to open them, I'm afraid they are encrypted and can only be decrypted here."
If I were you I'd raise a support ticket at https://www.dropbox.com/support
Okay everyone, I figured out why mine wasn't working.. which is funny becuase this directory has been on my Dropbox since 2012 yet I am just now having issues moving the files..
After the error.. it was always creating the empty directories and I noticed this:
drwxrwxr-x 2 tharris tharris 4096 Apr 6 2016 Musicdrwxrwxr-x 2 tharris tharris 4096 Aug 8 15:48 Persondrwxrwxr-x 2 tharris tharris 4096 Aug 8 15:44 RubymineProjectsdr-xr-xr-x 2 tharris tharris 4096 Jul 26 2016 SEP-MP5drwxrwxr-x 2 tharris tharris 4096 Aug 8 15:59 Softwaredrwxrwxr-x 2 tharris tharris 4096 Aug 8 15:44 Workdrwxrwxr-x 2 tharris tharris 4096 Aug 8 15:45 XonoticI went to the web interface and removed that shared drive from another Dropbox user.. went to move.. and no more error. So possibly if you have folders that are shared from other dropbox users, this may be whats causing issues with permissions so removing that at least gets data stored on bigger drive...By the way, after moving the drive, I readded that share via web interface and it seems to be syncing up but I have a while to go before I get all 500gb...Thanks Dropbox!
tharris104 wrote:
Okay everyone, I figured out why mine wasn't working.. which is funny becuase this directory has been on my Dropbox since 2012 yet I am just now having issues moving the files..
After the error.. it was always creating the empty directories and I noticed this:
drwxrwxr-x 2 tharris tharris 4096 Apr 6 2016 Musicdrwxrwxr-x 2 tharris tharris 4096 Aug 8 15:48 Persondrwxrwxr-x 2 tharris tharris 4096 Aug 8 15:44 RubymineProjectsdr-xr-xr-x 2 tharris tharris 4096 Jul 26 2016 SEP-MP5drwxrwxr-x 2 tharris tharris 4096 Aug 8 15:59 Softwaredrwxrwxr-x 2 tharris tharris 4096 Aug 8 15:44 Workdrwxrwxr-x 2 tharris tharris 4096 Aug 8 15:45 XonoticI went to the web interface and removed that shared drive from another Dropbox user.. went to move.. and no more error. So possibly if you have folders that are shared from other dropbox users, this may be whats causing issues with permissions so removing that at least gets data stored on bigger drive...Which means the problem you were encounting is completely different to the issue I'm encountering.
Just saying... you should check permissions on those empty directories.. or even on their website.. it will have a lock next to the icon.
tharris104 wrote:
Just saying... you should check permissions on those empty directories.. or even on their website.. it will have a lock next to the icon.
What empty directories?
I have no shared folders. I can reproduce the problem even after deleting everything in my Dropbox directory. I can move the Dropbox directory within ${HOME}. I think we have both encountered things that cause the Dropbox client to chuck out the same generic error message but the underlying issues are entirely different.
mike _. wrote:
What empty directories?
I have no shared folders. I can reproduce the problem even after deleting everything in my Dropbox directory. I can move the Dropbox directory within ${HOME}. I think we have both encountered things that cause the Dropbox client to chuck out the same generic error message but the underlying issues are entirely different.
You are probably right aboout that.. The directories I am talking about are created on the mount (or wherever your moving to) after trying to move the folders.. I was messing with mount points and actually ended up with my 2TB mounted inside home. But after looking at the empty folders, thats when I saw the permissions it was trying to move..
