Child Item

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?

Find more posts tagged with

Setting Up the Apps

Desktop

Install

Linux

Spam

Insightful

Accepted answers

Здравко

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)!

All comments

Здравко

eurico

Thanks for the reply! I'll check those links!

Здравко

Hello @Daphne,

Can you share to us: Will we alive to see, some day, that gets fixed? :thinking: :nerd:

Thanks. :slight_smile:

Daphne

Hey peeps, thanks for mentioning me here @Здравко!

I'd be more than happy to look further into this with you both, we'd need to have a look into this with some additional details so that we can troubleshoot with our specialists.

So that we can gather some device specific info, would you mind if I reached out to both of you, @eurico and @Здравко, via the email associated with your Community profiles?

If you've already submitted a ticket with the team, just let me know the ticket number (eg. #1234567).

Let me know and I hope you have a great weekend ahead - thanks!

eurico

Hi!
Sure, you can contact me via e-mail!
I haven't submitted a ticket yet. I was trying to solve this by myself, but nothing so far.
Is something about Application-Indicator-plugin on XFCE?

Здравко

Hi @Daphne,

I can't say anything more than described in links I have posted above. There, everything is described in details. About tickets... :laughing: I already have one (I have no idea why you can't see it) for something else, but "speed" is disappointing. :slight_frown: I can't add anything more. If that's not enough for your development (to fix the bug), fire them out.

Cheers!

Daphne

Thanks for getting back to me here peeps!

I've reached out to your email @eurico, please just check your inbox when you have a chance and we can do some investigation into this.

For me to be able to pass this along to the team, we would need to gather all the relevant info and send this to our specialist via our Support channel which is why I asked to reach out to you via email @Здравко.

If you'd like to help us with this and have the time, since I couldn't locate any open active tickets please feel free to create a new ticket here and let me know the ticket number.

Hope you both have a great day!

Здравко

Wow... Probably the Ticket #9534992 is closed. That's way I have no any new post from a while ago. Seems your "specialists" are no so specialists! As I already said, I can't add anything more. Of course, if you want, new ticket could be created, but I don't want to repeat everything again. All my system details are in the ticket mentioned above and all issue details are in the first link, also mentioned above. Just add them and note, if applicable, that I don't want meaningless post conversation, but entire information have to be posted to development. Conversation to "specialists" (in fact backend customer support with suspicious technical knowledge), no thanks. The information is enough for knowledgeable person.

Good luck to all of us! (will be need)

Daphne

Thanks for the ticket number @Здравко, I was able to locate it.

It seems that the ticket isn't closed, so I appreciate you nudging me on this.

I'll have a look into this from my side, but in the meantime, if you'd like an update on the status of your ticket you can reply back to the last communication there.

Cheers!

Здравко

I already have said everything I can. I believe that everything is clear. If there is something else I can add, You or somebody from backteam can ask me, I would be happy to help further. I want to note that statements, like a discrepancy related to feature description and actual feature are new feature request, is more than disappointing!