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
I'm getting an error message "Could not start the Dropbox daemon" for a Fedora 31 install.
Hello,
I tried to install dropbox on my fresh installation of Fedora 31. The error that i got is "Could not start the dropbox daemon" if i run the installation on terminal i got additional details ...
Hi, I just used this command on my Fedora 31 Workstaion before installing Dropbox. The Dropbox daemon starts successfully now, and the sync function works well.
sudo dnf install libatomic
Now the only problem is the tray icon keeps showing "Connecting...", but it does not affect the running.
Got the same issue on Kubuntu 18.04 (never seen this before). For debian based distros like Kubuntu/Ubuntu/etc, you can install build-essential pack that contains also required libatomic1:amd64 as mentioned ealier (and many other packages, like G++, GCC, dpkg-dev, make,etc) and is helpful for other things like compiling a Debian packages and so on.
Just run the following in terminal:
sudo apt update sudo apt install build-essential
Hi athan13,
If you aren't sure, don't post incorrectnessess, please. "build-essential" don't depends on "libatomic1"! About "gcc", "make" and others, they are mandatory parts of (almost) all Linux distributions. "dkms" kernel modules depends on them! About development packages, they aren't needed either to Dropbox or to user which don't plan to code something, but just wants to type some text or draw drawings, for example. :slight_smile:
Congratulations for your interest in coding, but this is off topic.
Hi Здравко ,
I'm sure about what I have seen:
And I also use "build-essential" package in cases I want to install other package that need a C/C++ compiler for example (as I mentioned before).
Usually it's the first thing I install in a fresh Ubuntu not only for coding purposes. And it's optional of course.
Hi athan13,
Sorry for the confusion, where seems I have involve you in! More full expression: I don't mean you aren't sure what you have seen, but what actually "build-essential" depends on. And Yes, You are NOT sure about direct dependencies (indirect could be any of course)! Just try:
dpkg-query -W -f='${Depends}\n' build-essentialWhat is the result? :thinking: :wink: Also other thing:
athan13 wrote:
... And it's optional of course.Why such thing (assume so important) could be optional? :thinking::wink: I fully agree "build-essential" package is very important (not for C/C++ coders only, but for all coders).
Wish you Happy coding!
