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
Linux Dropbox: fatal python exception
Hi everybody, I am new to linux, taking over responsibilty due to a colleague leaving and im very lost. Yesterday, I checked the drobox status on the terminal and it was stuck on dropbox upgrading....
Hi everyone,
On this thread different troubles are posted! Most of them are related to missing library assignment declaration (library package in fact). For Ubuntu and other debian derived packaging systems, package name is "libatomic1". For RPM based - "libatomic". Workaround to this Dropbox developers fault could be installing the corresponding package by hands. For example, installation command, in Ubuntu, is:
sudo apt-get install libatomic1
On other systems, equivalent commands could be used.
Hope this helps. :wink:
PS: On Fedora usable command is:
sudo dnf install libatomic
Hi everyone,
On this thread different troubles are posted! Most of them are related to missing library assignment declaration (library package in fact). For Ubuntu and other debian derived packaging systems, package name is "libatomic1". For RPM based - "libatomic". Workaround to this Dropbox developers fault could be installing the corresponding package by hands. For example, installation command, in Ubuntu, is:
sudo apt-get install libatomic1
On other systems, equivalent commands could be used.
Hope this helps. :wink:
PS: On Fedora usable command is:
sudo dnf install libatomic
This workaround fixed my issue. Thank you.
for me aswell
Hello
I had to install several packages in order to bypass the error, including libatomic bus as well :
libxshmfence-dev
libxcb-present-dev
libxcb-dri3-dev
libxcb-dri2-0-dev
libxcb-glx0-dev
libxdamage-dev
libxext6
libglapi-mesa
libatomic1That should be included in the package, dont you think ?
Hi Cortex76,
That's exactly what Dropbox tries to do (not always successfully). Such a strategy is very wrong! The only right way is proper declaration of needed packages, not include them in one place (systems change over time). The exact reason related to libatomic1 was missing declaration and Dropbox developers rely this package exists in all cases, which isn't true. What they do - not declare needed, but instead libatomic1 content gets included in the application. What's result - the Dropbox application package gets bigger and bigger over time, which could be avoided, nothing more.
