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
Andy Coda
4 years agoExplorer | Level 4
Couldn't start Dropbox permissions error
Hi,
My dropbox app won't open at all anymore. I get a Couldn't Open Dropbox message saying it's usually a permissions error. I've been through my shared folders on the webpage and checked and r...
- 4 years ago
Hi again Andy Coda,
The dummy file you have created seems Ok. That proves the issue is not in your default settings. It appears exactly as has to be. The commands you have executed, as listed, can't be a reason for the issue observed. Still not clear what could be the reason, but let's try fix it by hands. At the beginning what shows the list of troublesome folder? Post the result of:
ls -al /Applications/Dropbox.app/Contents/Frameworks/DropboxCrashpad.framework/Versions/A
Next try fix the problem using following commands:
sudo chown -R "$USER" /Applications/Dropbox.app
chmod -R a+r /Applications/Dropbox.app
chmod -R u+w /Applications/Dropbox.app
chmod -R go-w /Applications/Dropbox.appExecute the first (ls) command again. Is something changed? 🧐
Hope this helps.
HleeLee
Explorer | Level 3
I'm having the same issue. Except that I just used the Migration Assistant on my new laptop from a Time Machine backup. I found this other info, but it didn't work for me. So now I'm lost.
Здравко
4 years agoLegendary | Level 20
Hi HleeLee,
Take in mind that the initial error message is a template pretty same for almost all kind of critical issues Dropbox application encounters. The same message dialog definitely doesn't mean the same issue! When you are saying:
HleeLee wrote:I'm having the same issue. ...
... what do you actually mean? 🤔 Is it the same log text or not? The dialog is saying the same even if there is an issue not directly related to permission! 😉
Hope this clarifies matter, why so many different solutions related to the "same" message.
- HleeLee4 years agoExplorer | Level 3
To me, it looks very close to what the OP said (below).
I also attached a screen grab of the error popping up even after it says my permissions were fixed. I've also restarted after doing this, nothing changes. I've uninstalled and reinstalled. I reinstalled my OS (Big Sur). So far nothing has worked.
bn.BUILD_KEY: Dropbox
bn.VERSION: 118.4.460
bn.constants.WINDOWS_SHELL_EXT_VERSION: 47
bn.is_frozen: True
machine_id: 7995f91a-65d8-575a-8e97-d76493f7e6d2
pid: 1212
ppid: 1
uid: 503
user_info: pwd.struct_passwd(pw_name='HleeLeeKron', pw_passwd='********', pw_uid=503, pw_gid=20, pw_gecos='Hlee Lee Kron', pw_dir='/Users/HleeLeeKron', pw_shell='/bin/bash')
effective_user_info: pwd.struct_passwd(pw_name='HleeLeeKron', pw_passwd='********', pw_uid=503, pw_gid=20, pw_gecos='Hlee Lee Kron', pw_dir='/Users/HleeLeeKron', pw_shell='/bin/bash')
euid: 503
gid: 20
egid: 20
group_info: grp.struct_group(gr_name='staff', gr_passwd='*', gr_gid=20, gr_mem=['root', 'HleeLeeKron', '_nsurlstoraged', '_serialnumberd'])
effective_group_info: grp.struct_group(gr_name='staff', gr_passwd='*', gr_gid=20, gr_mem=['root', 'HleeLeeKron', '_nsurlstoraged', '_serialnumberd'])
DYLD_LIBRARY_PATH: None
cwd: '/'
real_path='/'
mode=0o40755 uid=0 gid=0
parent mode=0o40755 uid=0 gid=0
HOME: '/Users/HleeLeeKron'
appdata: '/Users/HleeLeeKron/.dropbox/instance1'
real_path='/Users/HleeLeeKron/.dropbox/instance1'
mode=0o40700 uid=503 gid=20
parent mode=0o40700 uid=503 gid=20
dropbox_path: '/Users/HleeLeeKron/Dropbox'
real_path='/Users/HleeLeeKron/Dropbox'
mode=0o40700 uid=503 gid=20
parent mode=0o40755 uid=503 gid=20
sys_executable: '/Applications/Dropbox.app/Contents/MacOS/Dropbox'
real_path='/Applications/Dropbox.app/Contents/MacOS/Dropbox'
mode=0o100755 uid=503 gid=20
parent mode=0o40755 uid=503 gid=20
trace.__file__: '/Applications/Dropbox.app/Contents/Resources/python-packages.zip/dropbox/client/ui/common/boot_error.pyc'
real_path='/Applications/Dropbox.app/Contents/Resources/python-packages.zip/dropbox/client/ui/common/boot_error.pyc'
not found
parent not found
tempdir: '/var/folders/dw/6ntvgsfs53b3pl_bl8746dhw0000gq/T'
real_path='/private/var/folders/dw/6ntvgsfs53b3pl_bl8746dhw0000gq/T'
mode=0o40700 uid=503 gid=20
parent mode=0o40755 uid=503 gid=20
Traceback (most recent call last):
File "dropbox/client/main.pyc", line 817, in wrapper
File "dropbox/client/main.pyc", line 6387, in finish_dropbox_boot
File "dropbox/client/main.pyc", line 5890, in _init_components_for_account
File "dropbox/client/main.pyc", line 5800, in create_sync_engine
File "dropbox/sync_engine_boundary/factory.pyc", line 239, in make_sync_engine
File "dropbox/sync_engine/nucleus/classic_client/sync_engine.pyc", line 295, in __init__
File "dropbox/sync_engine/nucleus/classic_client/modern_client/modern_client.pyc", line 176, in __init__
File "dropbox/sync_engine/nucleus/classic_client/modern_client/base.pyc", line 143, in __init__
File "dropbox/sync_engine/nucleus/classic_client/thin_adapter/in_proc.pyc", line 232, in __init__
File "dropbox/sync_engine/nucleus/classic_client/thin_adapter/in_proc.pyc", line 625, in _init_new_engine_locked
File "dropbox/sync_engine/nucleus/thin_client/client.pyc", line 206, in __init__
File "extensions/nucleus/nucleus_python.pyx", line 79, in nucleus_python.NucleusSyncEngine.__cinit__
nucleus_python.SyncEngineError: "Initializing engine |>> Initializing filesystem |>> Attempting to register icons |>> Opening dst |>> open syscall |>> Permission denied"- Здравко4 years agoLegendary | Level 20
HleeLee wrote:To me, it looks very close to what the OP said (below). ...
😁😆🙂 HleeLee, Do the actual error messages look the same:
Andy Coda wrote:Exception: should not give write permissions to other users for the module, /Applications/Dropbox.app/Contents/Frameworks/DropboxCrashpad.framework/Versions/A/DropboxCrashpad, loaded by Tungsten
HleeLee wrote:nucleus_python.SyncEngineError: "Initializing engine |>> Initializing filesystem |>> Attempting to register icons |>> Opening dst |>> open syscall |>> Permission denied"
What you would say? 🤔
In both cases permissions are involved, but completely different types and on completely different places! Your log is less informative HleeLee, causa missing exact place, so there are much more possibilities. It's clear only that the problem rise up within Dropbox folder for you (the "nucleus" engine works there). Reason could vary from antivirus protection triggered erroneous (check antivirus protection) up to your system puts Dropbox folder in "quarantine" (are there some unusual extended attributes falls from nowhere).... or similar.One thing you can try: rename your Dropbox folder to something like DropboxBackup. Create new Dropbox folder and copy all old content to the just created folder (copy NOT move, using move you would move possible unwanted attributes). Try run Dropbox application now. If everything works, you can wipe out the old folder. 😉
Might be there easier way, if we know exact reason and place, but no such information. Let's hope some day Dropbox development will improve error information (in the particular case what exactly "open" command is trying to open and the exact system error code received)... let's hope.
Hope this helps.
- HleeLee4 years agoExplorer | Level 3
I forgot the screen grab last post but I seemed to have figured it out.
I followed the info here: https://support.apple.com/en-us/HT208050
I changed from bash to zsh, restarted. Dropbox worked, but I couldn't save anything to the desktop. So then I changed it back from zsh to bash and now it all works. I hope it stays that way!
About Apps and Installations
Have a question about a Dropbox app or installation? Reach out to the Dropbox Community and get solutions, help, and advice from members.
Need more support
If you need more help you can view your support options (expected response time for an email or ticket is 24 hours), or contact us on X or Facebook.
For more info on available support options for your Dropbox plan, see this article.
If you found the answer to your question in this Community thread, please 'like' the post to say thanks and to let us know it was useful!