Dropbox app not starting up with WSL2 integrated

[aavitan]

bn.BUILD_KEY: Dropbox
bn.VERSION: 106.4.368
bn.constants.WINDOWS_SHELL_EXT_VERSION: 45
bn.is_frozen: True
machine_id: b7211f02-e7df-47d5-941c-dcd185a4add6
pid: 17140
cwd: 'C:\\Program Files (x86)\\Dropbox\\Client'
real_path='C:\\Program Files (x86)\\Dropbox\\Client'
mode=0o40777 uid=0 gid=0
parent mode=0o40777 uid=0 gid=0
HOME: None
appdata: 'C:\\Users\\aavitan\\AppData\\Local\\Dropbox\\instance1'
real_path='C:\\Users\\aavitan\\AppData\\Local\\Dropbox\\instance1'
mode=0o40777 uid=0 gid=0
parent mode=0o40777 uid=0 gid=0
dropbox_path: 'C:\\Users\\aavitan\\Dropbox'
real_path='C:\\Users\\aavitan\\Dropbox'
mode=0o40555 uid=0 gid=0
parent mode=0o40777 uid=0 gid=0
sys_executable: 'C:\\Program Files (x86)\\Dropbox\\Client\\Dropbox.exe'
real_path='C:\\Program Files (x86)\\Dropbox\\Client\\Dropbox.exe'
mode=0o100777 uid=0 gid=0
parent mode=0o40777 uid=0 gid=0
trace.__file__: 'C:\\Program Files (x86)\\Dropbox\\Client\\106.4.368\\python-packages.zip\\dropbox\\client\\ui\\common\\boot_error.pyc'
real_path='C:\\Program Files (x86)\\Dropbox\\Client\\106.4.368\\python-packages.zip\\dropbox\\client\\ui\\common\\boot_error.pyc'
not found
parent not found
TMP: C:\Users\aavitan\AppData\Local\Temp
TEMP: C:\Users\aavitan\AppData\Local\Temp
tempdir: 'C:\\Users\\aavitan\\AppData\\Local\\Temp'
real_path='C:\\Users\\aavitan\\AppData\\Local\\Temp'
mode=0o40777 uid=0 gid=0
parent mode=0o40777 uid=0 gid=0
Traceback (most recent call last):
File "dropbox\client\main.pyc", line 799, in wrapper
File "dropbox\client\main.pyc", line 6528, in finish_dropbox_boot
File "dropbox\client\main.pyc", line 6016, in _init_components_for_account
File "dropbox\client\main.pyc", line 5967, in create_sync_engine
File "dropbox\sync_engine_boundary\factory.pyc", line 267, in make_sync_engine
File "dropbox\sync_engine\nucleus\classic_client\sync_engine.pyc", line 349, in __init__
File "dropbox\sync_engine\nucleus\classic_client\modern_client\modern_client.pyc", line 190, in __init__
File "dropbox\sync_engine\nucleus\classic_client\modern_client\base.pyc", line 128, in __init__
File "dropbox\sync_engine\nucleus\classic_client\thin_adapter\in_proc.pyc", line 228, in __init__
File "dropbox\sync_engine\nucleus\classic_client\thin_adapter\in_proc.pyc", line 598, in _init_new_engine_locked
File "dropbox\sync_engine\nucleus\thin_client\client.pyc", line 151, in __init__
File "extensions\nucleus\nucleus_python.pyx", line 86, in nucleus_python.NucleusSyncEngine.__cinit__
nucleus_python.SyncEngineError: "Initializing engine |>> Initializing platform |>> Testing filesystem support |>> Filesystem \"wsl\" not supported! See dropbox.com/help/3 "

Seems like there is a issue with this network drive

[Jay]

Hi @aavitan, thanks for posting today!

I'm sorry to hear about this situation. It seems that the Dropbox desktop application is having issues during the installation. 

If you're not on a Dropbox Basic plan with more than 3 devices connected, could you try an advanced reinstall of the app using the steps in this link?
 

Let me know how it goes!

[aavitan]

not working, please don't send me to do stupid restarts

seems like WSL has integrated into windows a filesystem unrcongnized by dropbox and instead of skipping it, it fails and take the whole booting process with it.

Is this a known issue? was it already addressed and fix (if so, what version+build + attached link to installer)?

I have windows version 2004 with WSL2 over centos, with few vhdx drives, that somehow being detected by dropbox

you can address me any questions if needed

[Jay]

Is this the first time you've installed the Dropbox app? Did you move the Dropbox folder to the other file system, while the desktop app was installed on the Windows file system?

[aavitan]

I had Dropbox for at least one year installed
I didnt do anything that couldnt change the dropboy location in disk
The issues started right after installing WSL2

[Здравко]

Hi @aavitan,

I don't use WSL but seems somehow installation affect the way file system type gets represented (in fact has erroneously represented), according your description. This seems be a Microsoft bug, probably. Combined with the Dropbox' quirk - only limited set of file system types are acceptable... and voila - your issue. Is the usage of WSL2 really important for you? If not, a workaround could be usage of different virtualization system. 😉 What about VirtualBox, VMware, and ... others?! Or might be a different cloud provider (not so pretentious).

Hope this gives an idea.

PS: In addition to wrong file system declaration you have another problem - forbidden writing in Dropbox folder for Dropbox application. Review the permissions set to Dropbox folder.

[aavitan]

Hey

Unfortunately this is not a possibility
Its more realistic currently to migrate my dropbox data to google drive 😔

Ia it going to be solved by Dropbox soon?

[Jay]

Hi @aavitan, to look into this matter further, would it be possible to email you at the address associated with your forum profile? 

[aavitan]

yes of course

[Jay]

Thanks for the message, I've sent you an email, please could you reply to it when you get a chance.