Learn how to make the most out of the Dropbox Community here 💙.
Forum Discussion
Solved
Audio files not showing on Linux (Fedora) mounted directory.
I used headless install to install 178.4.4811 and executed .dropbox-dist/dropboxd. The folder shows the directory structure that I see when I use the browser. However some directories on the browser ...
Ahahh...😯 fredleason, you're falling in trap of one old Dropbox application bug. It's signaled multiple times for (I personally too), but nobody take care about yet. 🤷 Linux is not so important for Dropbox; this is confirmation once again.
The issue is that Dropbox rely on opening browser with script written in temporary file in temporary folder. All good, but in latest browser releases, working on Linux, this practice is considered insecure and is forbidden already. That's it; better don't rely this bug to be fixed soon.
Fortunately there is a workaround. Run in your terminal something like:
export DISPLAY= ~/.dropbox-dist/dropboxd
Next the initialization, you will be invited to open printed link. Using this link you can link your new install to your account. 😉
Hope this helps.
Add: There is chance the link not to work immediately; refresh your browser frame next couple of seconds.
I tried downloading and installing 179.4.4917. It does not install. When I run
[*******@fedora ~]$ sudo ./.dropbox-dist/dropboxdit stops processing 12 steps down at
dropbox: load fq extension '/home/*******/.dropbox-dist/dropbox-lnx.x86_64-179.4.4917/PyQt5.QtDBus.so'It appears others are having similar problems with that release.
Hi fredleason,
Yes, of course, it stops once all external modules get loaded. You posted the last module loaded that Dropbox Python interpreter loads. 😉 Since then (the initialization finish) regular Dropbox application work starts.
Why do you use 'sudo'? Dropbox usually use regular user context and no need to run it in superuser mode. Actually for any application (if not some system management tool), it's never good idea to run in superuser mode (can be dangerous). Dropbox definitely doesn't need it.
You didn't post your folder owner (it's masked), but is the owner there match to you? This can be an issue. If needed, reset all Dropbox file/folder properties (including owner). You can get additional info using 'dropbox status' (here 'dropbox' is the control script - it's preinstalled if you have installed using official package too; here can be downloaded by hand).
Good luck.
I removed sudo and the browser opened
Not sure how to check the client for a new one.
Ahahh...😯 fredleason, you're falling in trap of one old Dropbox application bug. It's signaled multiple times for (I personally too), but nobody take care about yet. 🤷 Linux is not so important for Dropbox; this is confirmation once again.
The issue is that Dropbox rely on opening browser with script written in temporary file in temporary folder. All good, but in latest browser releases, working on Linux, this practice is considered insecure and is forbidden already. That's it; better don't rely this bug to be fixed soon.
Fortunately there is a workaround. Run in your terminal something like:
export DISPLAY= ~/.dropbox-dist/dropboxd
Next the initialization, you will be invited to open printed link. Using this link you can link your new install to your account. 😉
Hope this helps.
Add: There is chance the link not to work immediately; refresh your browser frame next couple of seconds.
Thanks. Unfortunately, I got a Qt:Fatal
[*******@fedora ~]$ export DISPLAY=~/.dropbox-dist/dropboxd [*******@fedora ~]$ ./.dropbox-dist/dropboxd dropbox: load fq extension '/home/*******/.dropbox-dist/dropbox-lnx.x86_64-179.4.4917/cryptography.hazmat.bindings._openssl.abi3.so' dropbox: load fq extension '/home/*******/.dropbox-dist/dropbox-lnx.x86_64-179.4.4917/cryptography.hazmat.bindings._padding.abi3.so' dropbox: load fq extension '/home/*******/.dropbox-dist/dropbox-lnx.x86_64-179.4.4917/apex._apex.abi3.so' dropbox: load fq extension '/home/*******/.dropbox-dist/dropbox-lnx.x86_64-179.4.4917/psutil._psutil_linux.cpython-38-x86_64-linux-gnu.so' dropbox: load fq extension '/home/*******/.dropbox-dist/dropbox-lnx.x86_64-179.4.4917/psutil._psutil_posix.cpython-38-x86_64-linux-gnu.so' dropbox: load fq extension '/home/*******/.dropbox-dist/dropbox-lnx.x86_64-179.4.4917/tornado.speedups.cpython-38-x86_64-linux-gnu.so' dropbox: load fq extension '/home/*******/.dropbox-dist/dropbox-lnx.x86_64-179.4.4917/wrapt._wrappers.cpython-38-x86_64-linux-gnu.so' dropbox: load fq extension '/home/*******/.dropbox-dist/dropbox-lnx.x86_64-179.4.4917/PyQt5.QtCore.so' dropbox: load fq extension '/home/*******/.dropbox-dist/dropbox-lnx.x86_64-179.4.4917/PyQt5.sip.so' dropbox: load fq extension '/home/*******/.dropbox-dist/dropbox-lnx.x86_64-179.4.4917/PyQt5.QtGui.so' dropbox: load fq extension '/home/*******/.dropbox-dist/dropbox-lnx.x86_64-179.4.4917/PyQt5.QtWidgets.so' dropbox: load fq extension '/home/*******/.dropbox-dist/dropbox-lnx.x86_64-179.4.4917/PyQt5.QtDBus.so' b'!! (Qt:Fatal) QXcbConnection: Could not connect to display /home/*******/.dropbox-dist/dropboxd' XXX lineno: 938, opcode: 4 Segmentation fault (core dumped) [*******@fedora ~]$ echo $DISPLAY /home/*******/.dropbox-dist/dropboxdIt's strange because in my initial installation I did get a browser open with a key.
