Need to see if your shared folder is taking up space on your dropbox 👨💻? Find out how to check here.
Forum Discussion
Capatex
7 years agoHelpful | Level 5
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....
- 7 years ago
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
7 years agoHelpful | Level 5
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
Здравко
7 years agoLegendary | Level 20
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:
- Luis287 years agoHelpful | Level 5
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
- Здравко7 years agoLegendary | Level 20
Luis28 wrote:all right so back to the other package!
...
What you mean here? - "the other package"... Why back?
And result from following command:objdump -i $(whereis libatomic.so.1 | sed s/libatomic.so:\ //)
- Luis287 years agoHelpful | Level 5
What you mean here? - "the other package"... Why back?
i did install the 32 bit package of dropbox to test if it does make a differance. It did not, so i will install the right one for my PC's architecture again!
(while installing the following message pops up:error: can't create transaction lock on /var/lib/rpm/.rpm.lock (Resource temporarily unavailable) error: -: key 1 import failed.
dont know what it means and if it might be relevant ...
)
Output from "objdump -i $(whereis libatomic.so.1 | sed s/libatomic.so:\ //)" is:
BFD header file version version 2.32-29.fc31 elf64-x86-64 (header little endian, data little endian) i386 elf32-i386 (header little endian, data little endian) i386 elf32-iamcu (header little endian, data little endian) iamcu elf32-x86-64 (header little endian, data little endian) i386 pei-i386 (header little endian, data little endian) i386 pei-x86-64 (header little endian, data little endian) i386 elf64-l1om (header little endian, data little endian) l1om elf64-k1om (header little endian, data little endian) k1om elf64-little (header little endian, data little endian) i386 l1om k1om iamcu plugin elf64-big (header big endian, data big endian) i386 l1om k1om iamcu plugin elf32-little (header little endian, data little endian) i386 l1om k1om iamcu plugin elf32-big (header big endian, data big endian) i386 l1om k1om iamcu plugin pe-x86-64 (header little endian, data little endian) i386 pe-bigobj-x86-64 (header little endian, data little endian) i386 pe-i386 (header little endian, data little endian) i386 plugin (header little endian, data little endian) srec (header endianness unknown, data endianness unknown) i386 l1om k1om iamcu plugin symbolsrec (header endianness unknown, data endianness unknown) i386 l1om k1om iamcu plugin verilog (header endianness unknown, data endianness unknown) i386 l1om k1om iamcu plugin tekhex (header endianness unknown, data endianness unknown) i386 l1om k1om iamcu plugin binary (header endianness unknown, data endianness unknown) i386 l1om k1om iamcu plugin ihex (header endianness unknown, data endianness unknown) i386 l1om k1om iamcu plugin elf64-x86-64 elf32-i386 elf32-iamcu elf32-x86-64 pei-i386 pei-x86-64 i386 elf64-x86-64 elf32-i386 ----------- elf32-x86-64 pei-i386 pei-x86-64 l1om ------------ ---------- ----------- ------------ -------- ---------- k1om ------------ ---------- ----------- ------------ -------- ---------- iamcu ------------ ---------- elf32-iamcu ------------ -------- ---------- plugin ------------ ---------- ----------- ------------ -------- ---------- elf64-l1om elf64-k1om elf64-little elf64-big elf32-little elf32-big i386 ---------- ---------- elf64-little elf64-big elf32-little elf32-big l1om elf64-l1om ---------- elf64-little elf64-big elf32-little elf32-big k1om ---------- elf64-k1om elf64-little elf64-big elf32-little elf32-big iamcu ---------- ---------- elf64-little elf64-big elf32-little elf32-big plugin ---------- ---------- elf64-little elf64-big elf32-little elf32-big pe-x86-64 pe-bigobj-x86-64 pe-i386 plugin srec symbolsrec verilog i386 pe-x86-64 pe-bigobj-x86-64 pe-i386 ------ srec symbolsrec verilog l1om --------- ---------------- ------- ------ srec symbolsrec verilog k1om --------- ---------------- ------- ------ srec symbolsrec verilog iamcu --------- ---------------- ------- ------ srec symbolsrec verilog plugin --------- ---------------- ------- ------ srec symbolsrec verilog tekhex binary ihex i386 tekhex binary ihex l1om tekhex binary ihex k1om tekhex binary ihex iamcu tekhex binary ihex plugin tekhex binary ihex
Thank you for yout time, really appriciate it
About Create, upload, and share
Find help to solve issues with creating, uploading, and sharing files and folders in Dropbox. Get support and advice from the Dropbox Community.
The Dropbox Community team is active from Monday to Friday. We try to respond to you as soon as we can, usually within 2 hours.
If you need more help you can view your support options (expected response time for an email or ticket is 24 hours), or contact us on X, Facebook or Instagram.
For more info on available support options for your Dropbox plan, see this article.
If you found the answer to your question in this Community thread, please 'like' the post to say thanks and to let us know it was useful!