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
Need to "download proprietary daemon" every time Xubuntu restart.
I have installed Dropbox successfully on Xubuntu 19.10 using the 64-bit .deb installer from from https://www.dropbox.com.
But there is a problem, because every time Xubuntu restarts appears a pop-up window from Drobox saying "Dropbox is the easiest way to share ... to blablabla... you must download proprietary daemon ... blablabla". This happens every time the system starts. And then I click ok, the daemon gets intalled again and Dropbox works fine. Sometimes, I click cancel and Dropbox works fine too, but in some opportunities by clicking cancel Dropbox does not works. All the Dropbox requirements are ok, my machine configs are ok too.
So my question is, what is the problem? And how can I solve this?
Ooh, Yes. That's known bug in the control script. I have signaled long time ago, but no fix yet. Dropbox development don't care about. Easiest way is ignore such messages and always reject new install (it's already installed in fact). Another way is introducing delay in launching after restart. In fact due to heavy initial load, the script can't detect the working daemon and decides that it's not installed (incorrect).
PS: For more details related to the issue, take a look on a thread where that's widely discussed (almost monolog in fact). One possible solution (for the current trouble and for FS restrictions, together) could be used a proposed script which take care for everything. Take care for some variable names, erroneously renamed from "dropboxforum" platform (one more bug, also known). Just set the correct name (as noted below the script)!
Ooh, Yes. That's known bug in the control script. I have signaled long time ago, but no fix yet. Dropbox development don't care about. Easiest way is ignore such messages and always reject new install (it's already installed in fact). Another way is introducing delay in launching after restart. In fact due to heavy initial load, the script can't detect the working daemon and decides that it's not installed (incorrect).
PS: For more details related to the issue, take a look on a thread where that's widely discussed (almost monolog in fact). One possible solution (for the current trouble and for FS restrictions, together) could be used a proposed script which take care for everything. Take care for some variable names, erroneously renamed from "dropboxforum" platform (one more bug, also known). Just set the correct name (as noted below the script)!
