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.
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. I restarted it and now I'm getting the following error with a load of other text:
ImportError: libatomic.so.1: cannot open shared object file: No such file or directory
!! dropbox: fatal python exception:
Can anybody advise how I am able to fix this? And please bear in mind I am new to all of this 🙂
Thank you so much for your time.
Ross
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:\ //)
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
@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:\ //)
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
@Luis28 wrote: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 ...
)
Yes definitely is relevant. Your initial error report is produced from 64-bit version, that confused me. I thought that it's still so, but...
Seems you have still running some package management program and you try run second one - that's restricted! Make sure all package management tools are closed before to try reinstall. Only one such application (package manager) can run at every one moment.
libatomic.so.1 - seems correct version.
ooh my bad
but it seems that i cant find that second instance ...
i thoughnt it might be the dnfdragora running (never used it just autostarted), i closed that, removed it along with dropbox and rebooted ... then while installing dropbox, same error
As a "test" i installed gparted from the repo, that installed without any issues.
any idea on how to fix that?
If the error message prodused is the same - i.e. import error for libatomic.so.1, not other library, for example - I have no more ideas. Sorry.
sadly it is ...
well neverthless, thank you for your time and suggestions 🙂
i now do have an other error to research so maybe that helps 🙂
Hey @Luis28!
Sorry to hear the issue is ongoing. You got the help of the best Linux user we have in the Community (no offence to the rest of our Linux users. This is just my opinion). I was confident that this would get solved with the help of Здравко. No worries though, there are still things we can do to help!
I can create a ticket for you and forward it to our specialised agents to take a look at device traces and help you further with this.
Let me know if you want me to do this. It would be my pleasure.
Cheers.
Fiona
Community Moderator @ Dropbox
dropbox.com/support
Did this post help you? If so, please give it a Like below.
Did this post fix your issue/answer your question? If so please press the 'Accept as Solution' button to help others find it.
Still stuck? Ask me a question! (Questions asked in the community will likely receive an answer within 4 hours!)
Hey @Fiona,
i appriciate your concerne, please do open a ticket for me. If you belive he was my best shot whithin the community than i will gladly accept the help of one of your agents 🙂
best,
Luis
Hi there!
If you need more help you can view your support options (expected response time for a ticket is 24 hours), or contact us on X or Facebook.
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!