We are aware of the issue with the badge emails resending to everyone, we apologise for the inconvenience - learn more here.
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.
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:
I have the same issue. Your steps require Dropbox to remain open, but the error dialog is modal and prevents access to the Preferences UI. When you close the error dialog, the entire application closes.
- Ed
Dropbox Staff
Hi Guy
Could you please follow these steps:
On your Dropbox client (desktop version):
- Click on the Dropbox icon and then the "gear" at the bottom right
- Open the Preferences pane
- Click the Account tab.
- Hold down the Option key and the "Unlink This Computer" button will become a "Fix Permissions" button.
- Click the Fix Permissions button and quit Dropbox.
- Restart your computer.
This should fix the problem. If you're still having problems, please let me know.
I had the same problem. I've already unlink and fix the permission. But the issues still happens.
- Rich
The "error" in your screenshot isn't the actual error. It's the test file that contains the error message. Open that file in a text editor and past the content here.
Respond to latest answer. My tab will not change, how long do i need to hold the option key? It stays in " Unlink this computer".
Thanks Rich!
I had the same problem on server 12 what i did was to just over install the software meaning install the application without removing the previous instillation that worked for me
