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
Why am I getting a 'Couldn't start Dropbox' permission error?
Here's the message that I get:
Couldn't start Dropbox.
This is usually because of permission error. Storing your home folder on a network share can also cause an error.
This often happens with users who may have migrated old data and settings from another Mac to their current computer.
Operating system permissions prevent files from being viewed or edited by unauthorized logins. Permissions can be set any number of ways and can be restored manually through a fairly simple process. Please note that it is very important to follow these steps specifically as failure to do so may result in other issues. On a Mac OS X you can do the following:
1) Make sure the Dropbox desktop application is running
2) Click on the Dropbox icon in your menu bar and then click your profile picture or initials
3) Select 'Preferences'
4) Click on the 'Account' tab
5) Hold down the 'Option/Alt' key
6) Click on the 'Fix Permissions' button (make sure you're still holding down the 'Option' key.
This will allow Dropbox access to your home folder, Dropbox folder, and any required settings.
Sorry Kaz, I don't understand you answer. I can't open the Dropbox application so I can't get past step 1 in your instructions.
I had the same problem after migrating data and settings to a new Mac. I tried to uninstall and then reinstall Dropbox, but still no luck. What finally did the trick was removing the Dropbox application settings. Instructions are in the Dropbox Help Center, under For Advanced Users:
- THANK YOU!
- Kaz
Dropbox Staff
This often happens with users who may have migrated old data and settings from another Mac to their current computer.
Operating system permissions prevent files from being viewed or edited by unauthorized logins. Permissions can be set any number of ways and can be restored manually through a fairly simple process. Please note that it is very important to follow these steps specifically as failure to do so may result in other issues. On a Mac OS X you can do the following:
1) Make sure the Dropbox desktop application is running
2) Click on the Dropbox icon in your menu bar and then click your profile picture or initials
3) Select 'Preferences'
4) Click on the 'Account' tab
5) Hold down the 'Option/Alt' key
6) Click on the 'Fix Permissions' button (make sure you're still holding down the 'Option' key.
This will allow Dropbox access to your home folder, Dropbox folder, and any required settings.
- Kaz
@ John, could you try the following? It is another way to repair your permissions:
1) Select your home directory (the folder named after your computer's login) and press Command-I to "Get Info"
2) Scroll down to the "Sharing & Permissions" section at the bottom of the Get Info window
3) If everything is grayed out, click on the gold lock at the bottom right of the window. You'll be prompted for your login password. You'll need admin access to edit the permissions. If you are unable to unlock these privileges, talk to your system administrator to give you access to this folder.
4) Your name should already be on the list of sharing and permissions. If you aren't listed, then add yourself by clicking the + button.
5) Once your user is added, click your name and then click the gear menu at the bottom middle of the window, and choose "Make me the owner". If this option is grayed out you can skip to step 6.
6) Click the gear again and choose "Apply to enclosed items".Had the same problem and tried all steps in above without success. The Mac said that I didn't have permission to do any changes. I think it is because I have migrated files across from a PC and I have seen similar issues before. However, I resolved it by in the home folders information section, instead of changing permissions unlock the folder in the general section at the top showing free space etc. and that worked for me.
I've just installed dropbox and got the same error message when I tried to start it.
Hi I can't start dropbox on my laptop. I get this message
"Couldn't start Dropbox This is usually because of a permissions error. Storing your home folder on a network share can also cause an error."
I had a previous version running fine. so I uninstalled it and installed the latest version from dropbox website. Then it told me the folder dropbox already existed and it will be renamed and I clicked install. That's all I know. It has also referenced a log file and I have pasted the contents of this below.
Please help I just upgraded to a pro account earlier today
bn.BUILD_KEY: Dropbox
bn.VERSION: 3.0.5
bn.DROPBOXEXT_VERSION: 24
bn.is_frozen: True
pid: 2308
cwd: u'C:\Users\Guy\AppData\Roaming\Dropbox\bin'
real_path=u'C:\Users\Guy\AppData\Roaming\Dropbox\bin'
mode=040777 uid=0 gid=0
parent mode=040777 uid=0 gid=0
HOME: u'C:\Users\Guy'
appdata: u'C:\Users\Guy\AppData\Roaming\Dropbox\instance2'
real_path=u'C:\Users\Guy\AppData\Roaming\Dropbox\instance2'
mode=040777 uid=0 gid=0
parent mode=040777 uid=0 gid=0
dropbox_path: u'C:\Users\Guy\Dropbox'
real_path=u'C:\Users\Guy\Dropbox'
mode=040777 uid=0 gid=0
parent mode=040777 uid=0 gid=0
sys_executable: 'C:\Users\Guy\AppData\Roaming\Dropbox\bin\Dropbox.exe'
real_path='C:\Users\Guy\AppData\Roaming\Dropbox\bin\Dropbox.exe'
mode=0100777 uid=0 gid=0
parent mode=040777 uid=0 gid=0
trace.file: 'C:\Users\Guy\AppData\Roaming\Dropbox\bin\Dropbox.exe\dropbox\client\ui\common\boot_error.pyc'
real_path='C:\Users\Guy\AppData\Roaming\Dropbox\bin\Dropbox.exe\dropbox\client\ui\common\boot_error.pyc'
not found
parent not found
TMP: C:\Users\Guy\AppData\Local\Temp
TEMP: C:\Users\Guy\AppData\Local\Temp
tempdir: u'c:\users\guy\appdata\local\temp'
real_path=u'c:\users\guy\appdata\local\temp'
mode=040777 uid=0 gid=0
parent mode=040777 uid=0 gid=0
Traceback (most recent call last):
File "dropbox\client\authenticate.pyc", line 1285, in authentication_thread
File "dropbox\client\authenticate.pyc", line 404, in finish_dropbox_boot
File "dropbox\sync_engine\sync_engine.pyc", line 484, in mount_dropbox_folder
File "dropbox\sync_engine\block_cache.pyc", line 35, in init
File "dropbox\sync_engine\block_cache.pyc", line 41, in compute_max_size
File "dropbox\sync_engine_file_system\windows.pyc", line 182, in wrapped
File "contextlib.pyc", line 35, in __exit_
File "dropbox\sync_engine_file_system\util.pyc", line 94, in convert_error
File "dropbox\sync_engine_file_system\windows.pyc", line 182, in wrapped
File "dropbox\sync_engine_file_system\windows.pyc", line 442, in get_disk_space_info
FSInvalidArgumentError: [Errno 22] The file or directory is corrupted and unreadable.Ed - your solution is not useful for clients who "couldn't start Dropbox", as per the title of this thread.
I've encountered this error after changing the user folder shortname (and account names) of an OS X user. Now unable to launch Dropbox or reinstall as it repeatedly tries to follow a folder path that no longer exists.
I've cleaned all the preference files I could find, can you please let me know where to find the file that the Dropbox app is referencing for the bad folder path so I can simply remove it and reinstall.
I have this issue too. The client will not launch
Could start Dropbox: https://www.evernote.com/l/AEH6CprAHDpIFoRW4_vdVregUExGriG4gB0It is trying to launch from the path: '/Users/tRavI/Dropbox'
However the path it should be launching from is '/Users/tRavIs/Dropbox'
There needs to be an "s" in the "tRavIs" directory. How do I update this path?- Rich
Super User II
I've encountered this error after changing the user folder shortname (and account names) of an OS X user. Now unable to launch Dropbox or reinstall as it repeatedly tries to follow a folder path that no longer exists.
See here:
Guys, I tried both the suggestions, however Kathy T's version was spot on! Resolved the problem. Superb.You guys are awesome. Thanks
Thanks Kathy - I tried that but it couldn't find the folder. Thanks Kaz, your solution worked fine.
@Kathy T.
Thanks
Worked for meThanks Kathy - worked for me!
