We are aware of the issue with the badge emails resending to everyone, we apologise for the inconvenience - learn more here.
Forum Discussion
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.
Hi Briain,
Glad to hear that helped you. 😉 I want clarify some possible terms mistakes and bad practices.
Briain wrote:..., but it's worth noting that if you've already installed the Dropbox application, ...
If you haven't Dropbox application already installed (including the daemon; it happens on first try launch), you can't do anything described above. So it's mandatory the application (more precisely the daemon) be installed in advance.
Briain wrote:..., right click on the application (on your task manager) and elect to close it, then run the two lines in the terminal ...
Dropbox application (again - more precisely the daemon) is a singletion application (may have only one running instance or it's supposed to be at least). If there is already running application instance, you shouldn't be able run another one (or least within the same user context)! So you should make sure it's so - either autorun isn't active or (as you noted) close already running instance - might be better using 'Quit Dropbox' entry in the icon context menu or 'dropbox stop' command in terminal instead of forcibly killing/terminating (through some task manager or in any other way).
Have a nice day.
Hi Здравко
Thank you for clarifying these points; most appreciated! I've edited the original post (with a note to explain why I've edited it and with a reference to your above post) in case anyone stumbles across it, without thinking to move onto the next forum page and read further.
Have a great day, too!
🙂
