Need to see if your shared folder is taking up space on your dropbox 👨💻? Find out how to check here.
Forum Discussion
Solved
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 recreate problem:
- Dropbox directory is currently ~/Dropbox
- Start Dropbox application by running ~/.dropbox-dist/dropboxd
- Right click sys tray icon and select Preferences.
- Click "Move…" button under Account > Location
- Select directory /local on which my user has write permissions.
- The message "Unexpected errors occurred. Your Dropbox is ok!" appears.
Observations:
- The directory /local/Dropbox is sucesfully created.
- One of the directories in ~/Dropbox is created in /local/Dropbox/ It's empty. Deleting that directory from ~/Dropbox before attempting the move doesn't help.
- Selecting other directories on which my user has write permissions results in the same behaviour.
- Permissions and ownership of my Dropbox directory and user's home directory are OK. (Troubleshooting advice for Linux at https://help.dropbox.com/desktop-web/move-dropbox-folder is pooly written. sudo is not needed on all those commands. "Internet menu" is not a thing in all (any?) desktop environments.)
- There's a log file in ~/.dropbox/logs/1 but it's a binary blob so useless without something to make it human readable and I can't locate such a thing.
- Deleting all my files from ~/Dropbox/ waiting for sync to complete and then attempting the move doesn't help.
- When attemping the move after deleting all my files from ~/Dropbox/ /local/Dropbox/.dropbox.cache/ is succesfully created. It's empty.
- Pausing syncing before attempting the move doesn't help.
- There don't seem to be any options that can be passed to ~/.dropbox-dist/dropboxd to get more info. (Adding --help prevents it running!)
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)
66 Replies
Replies have been turned off for this discussion
Hi Mike new ticket raised. F YI : https://dropbox.zendesk.com/hc/fr/requests/6332540. let's hope this moves this issue up the food chain. .
I have a virtualbox running WIN7 , witha shared folder, sync is working.. Minor provlem of with file conflicts - but hey, I'll just wait until the sync is 100% and then sort the file duplications.
Same problem... A possible workarround is to do it by a simlink :
- dropbox stop
- mv <old_path>/Dropbox <new_path>/Dropbox
- ln -s <new_path>/Dropbox <old_path>/Dropbox
- dropbox start
- Good idea LeviEE. I'll try soon.
Thanks. Same issue here. I am on Fedora and want to move the Dropbox folder from the default location at my SSD (with only 128gb) to another internal HDD. I use the Dropbox Desktop App graphical interface, it actually creates the Dropbox folders and the first level folders insided it, but do not move any file and show the error "Error moving Dropbox: Unexpected errors occurred"
By this time I am sure it is a bug. I just opened a ticket.
I'd already attempted this, both as a user & root
tried chmod 1777, to remove any risk of permissions restrictions.
Created new Group "dropbox" added root, sudo and users to group. linked
Created firewall rules,
Disabled the firewall.. +cold booted
Removed user install and reInstalled Dropbox as "Root" and even as root I cannot move Dbox folder to HDD
sadly nothing has worked : erm... YET...
pix365 wrote:
I'd already attempted this, both as a user & root
tried chmod 1777, to remove any risk of permissions restrictions.
Created new Group "dropbox" added root, sudo and users to group. linked
Created firewall rules,
Disabled the firewall.. +cold booted
chmod 1777 on what? 1777 on a directory means that any user can write to it but they can only delete things in it which they own. If you want to eliminate permissions as a problem it's not the most useful thing to set.
You may as well grab a couple fists full of straws as mess with the firewall and "Created firewall rules" doesn't convey anything of value about what you actually did.l
But whatever, it's clearly a bug in the Dropbox client.
Sadly the ticket I had open about this issue was closed by Drobox support without informing me or fixing the issue. I only found it it had been closed because I received a " tell us how we did" email, thought that was odd and then checked the status for the ticket. (The " tell us how we did" email didn't say that it was being sent as a result of ticket being closed, or mention a ticket number or anything useful like that.)
my attempt at isolating the issue has clearly upset you. Sorry.
Yes - one could say my attemps are clutching at straws, But any diag - even a faiure is better than doing nothing. The Dropbox folder is created yet fails to use it.. so i'm thinking why? what could prevent it. and without the ability to read the log files = my straws
it could have been the firewall rules. but i wasn't.
It could have been file (user and or group)permissons, but i isn't.
What directory do your think i'm attempting the chmod on? It's the new Dropbox folder on the other HDD. (why change anything else)
I am not recommending folks do this chmod to their files sytem, as your 100% right it is a dangerous chmod, it was a simple diagnostic step that failed to make any difference.
Well, I seem to have a similar setup to "mike", and the same problem. I have just submitted a new support ticket (I think).
- Mark
Super User II
mike _. wrote:Sadly the ticket I had open about this issue was closed by Drobox support without informing me or fixing the issue. I only found it it had been closed because I received a " tell us how we did" email, thought that was odd and then checked the status for the ticket. (The " tell us how we did" email didn't say that it was being sent as a result of ticket being closed, or mention a ticket number or anything useful like that.)Hi mike _., thats not helpful at all..... sorry.
I dont work for Dropbox, but, if you can get me a ticket number I'll see if I can escalate it for you.
The previous ticket number (issued by "mike") is 6168712. He wrote that earlier in the thread.
My ticket number is 6702220.
