We are aware of the issue with the badge emails resending to everyone, we apologise for the inconvenience - learn more here.
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
Luis28 wrote:...
i followed the solution and tried to install:sudo dnf install libatomic*but all packages where already installed.
...
Hi Luis28,
Are you sure?! :grinning::grin:
Note here no file name is denoted, but package name! Accordingly the wildcards have different meaning here, little bit! Wildcard use is good thing to list different package names installed, for example, but no to install something. Use the exact name (without the star in particular). And be more careful what's the result in terminal. :wink: Maybe you have ignored something before.
Good luck.
Hey Здравко,
I am shure, i did run the "sudo dnf install libatomic" command as suggested in the solution first, but get the message:
Package libatomic-9.2.1-1.fc31.i686 is already installed. Dependencies resolved. Nothing to do. Complete!
so i belive it is installed. I had a similar issue where installing all wildcards helped, due to the fakt that i needed the development pakage or something like this, thats why i tryed that here again.
I just noticed, it is the i686 pakaged, and i installed dropbox for 86_64 systems, could that be an issue?
(EDIT: installing the 32Bit dropbox package did result in the same errormessage)
I had another look at the terminal output, as far as i can see the error is a python exception, wich results form the Import Error of libatomic.so.1 (cannnot open / missing):
! 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 \n', ' File "dropbox/sync_engine/nucleus/classic_client/thin_adapter/in_proc.pyc", line 98, in \n', ' File "dropbox/sync_engine/nucleus/classic_client/wrapped_thin_client.pyc", line 26, in \n', ' File "dropbox/sync_engine/nucleus/thin_client/client.pyc", line 28, in \n', ' File "dropbox/foundation/metrics/amp/remote_sink.pyc", line 10, in \n', 'ImportError: libatomic.so.1: cannot open shared object file: No such file or directory\n'] (error 3)
Thanks for the repply tho :)
hope you have an other suggestion up ur sleve
First, the Dropbox package and the library package should match your architecture! After that, to see what's going on exactly, what is the result from:
ls -l $(whereis libatomic.so.1 | sed s/libatomic.so:\ //)
:thinking:
all right so back to the other package!
as a result i get:
rwxrwxrwx. 1 root root 18 Aug 27 19:18 /usr/lib/libatomic.so.1 -> libatomic.so.1.2.0
