Need to see if your shared folder is taking up space on your dropbox 👨💻? Find out how to check here.
Forum Discussion
Solved
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: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 :grinning::laughing: definitely is relevant. Your initial error report is produced from 64-bit version, that confused me. I thought that it's still so, but... :wink:
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. :wink:
libatomic.so.1 - seems correct version.
ooh my bad :see_no_evil:
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. :slight_frown: 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 :)- Fiona
Dropbox Staff
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.
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- Fiona
Thanks Luis. I appreciate the kind response of yours after all this troubleshooting.
Truth is that after the steps Здравко offered there are not much to add without checking device specific details. I think this will be the best way to address this.
You got mail! :envelope: :slight_smile:
Luis28, One last check to see if by error your library don't match 64-bits:
file -L $(whereis libatomic.so.1 | sed s/libatomic.so:\ //)
The result should contain "ELF 64-bit LSB shared object". If result contain "ELF 32-bit LSB shared object" or nothing similar at all, there is something wrong in the library installation/configuration. In such a case the package, containing the library, have to be reinstalled.
Good luck. :sunglasses:
