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 like "libatomic.so.1: cannot open shared object file: No such file or directory" Ps. on my previous version of linux (Zorin os) the dropbox application was working perfectly (so my requirement of my laptop are ok)
Tank you very much
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.
- Jane
Dropbox Staff
Hi, I suppose this issue is somehow caused by the new upgrade of Dropbox which shows a new version number 85.4.155 at the directory ~/.dropbox-dist/dropbox-lnx.x86_64-85.4.155 .
For I can remember, the version number was 84.4.170 before I reinstalled Fedora 31 yesterday, and it worked.
I tried to install Dropbox via both Fedora repo and the rpm package proived by Dropbox, but all failed at the point of starting Dropbox daemon.
Hope this helps.
I had to install libatomic1 manually:
sudo apt-get install libatomic1
fyi- this problem started for me when upgrading to 85.4.155
Hi, currently i'm getting same problem, How can we solve it on Fedora 31?
When I try to run `dropbox start` with the latest linux client 85.4.155, I get this error, and neither dropbox nor the dropbox systray icon start successfully:
dropbox: load fq extension '/home/tedm/.dropbox-dist/dropbox-lnx.x86_64-85.4.155/linuxffi.gnu.compiled._linuxffi_gnu.cpython-37m-x86_64-linux-gnu.so' Traceback (most recent call last): File "dropbox/client/main.pyc", line 7919, in main File "dropbox/client/main.pyc", line 7843, in main_startup File "dropbox/client/main.pyc", line 942, in __init__ File "dropbox/sync_engine_boundary/factory.pyc", line 147, in make_default_file_system File "dropbox/sync_engine_boundary/factory.pyc", line 99, in __init__ File "dropbox/sync_engine_boundary/factory.pyc", line 118, in _initialize_classes File "dropbox/sync_engine/nucleus/classic_client/sync_engine.pyc", line 276, in <module> File "dropbox/sync_engine/nucleus/classic_client/thin_adapter/in_proc.pyc", line 98, in <module> File "dropbox/sync_engine/nucleus/classic_client/wrapped_thin_client.pyc", line 26, in <module> File "dropbox/sync_engine/nucleus/thin_client/client.pyc", line 28, in <module> File "dropbox/foundation/metrics/amp/remote_sink.pyc", line 10, in <module> ImportError: libatomic.so.1: cannot open shared object file: No such file or directory !! dropbox: fatal python exception: ['Traceback (most recent call last):\n', ' File "dropbox/client/main.pyc", line 7919, in main\n', ' File "dropbox/client/main.pyc", line 7843, in main_startup\n', ' File "dropbox/client/main.pyc", line 942, in __init__\n', ' File "dropbox/sync_engine_boundary/factory.pyc", line 147, in make_default_file_system\n', ' File "dropbox/sync_engine_boundary/factory.pyc", line 99, in __init__\n', ' File "dropbox/sync_engine_boundary/factory.pyc", line 118, in _initialize_classes\n', ' File "dropbox/sync_engine/nucleus/classic_client/sync_engine.pyc", line 276, in <module>\n', ' File "dropbox/sync_engine/nucleus/classic_client/thin_adapter/in_proc.pyc", line 98, in <module>\n', ' File "dropbox/sync_engine/nucleus/classic_client/wrapped_thin_client.pyc", line 26, in <module>\n', ' File "dropbox/sync_engine/nucleus/thin_client/client.pyc", line 28, in <module>\n', ' File "dropbox/foundation/metrics/amp/remote_sink.pyc", line 10, in <module>\n', 'ImportError: libatomic.so.1: cannot open shared object file: No such file or directory\n'] (error 3) /usr/bin/dropbox:316: PyGTKDeprecationWarning: The keyword(s) "type, message_format" have been deprecated in favor of "message_type, text" respectively. See: https://wiki.gnome.org/PyGObject/InitializerDeprecations
UPDATE:I can't seem to reply to my own message, so I'll write an update. I guess dropbox got a new dependency with version 85.4.155 - it now requires libatomic. I installed that and it all works.
- Jane
I installed Dropbox onto Ubuntu 18.04 LTS, but am receiving this error. The computer does meet the minimum system requirements. Can someone please assist me?
- Jane
yes, it immediately worked when I installed that dependency.
Hi,
I went to the downloads page for and downloaded the Linux Ubuntu 64 deb file. It doesn't say anything on the Dropbox downloads page about needing to install anything else, and doesn't provide a link. So why is this message coming up? And what does the gibberish message about python3 mean? . Can someone please explain this?
About the stupid and meaningless message, take a look here https://www.dropboxforum.com/t5/Installs-integrations/Need-to-quot-download-proprietary-daemon-quot-every-time-Xubuntu/m-p/380239#M83397 😉. Hope this helps.
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.
