Tag Info

New answers tagged

1

Since you were apparently able to launch bash, you have the basics right: you need to copy all the libraries listed by ldd /bin/command to a directory on the library load path, plus the loader itself (/lib64/ld-linux-x86-64.so.2) which needs to be at the location hard-coded in the executables. If you get the error error while loading shared libraries: ...


1

try mkdir lib/x86_64-linux-gnu cp /lib/x86_64-linux-gnu/libtinfo.so.5 /lib/x86_64-linux-gnu/libdl.so.2 /lib/x86_64-linux-gnu/libc.so.6 lib/x86_64-linux-gnu If you whish to use commands like ls, you also have to ldd /bin/ls and copy library file. by the way, cp will copy the content of a symbolic link.


0

Careful. Shared library files are usually symlinked. This way the current version can be changed and all the installed applications can still find it. For instance, on my system: ls -l /usr/lib/libc.so.6 lrwxrwxrwx 1 root root 12 dec 27 03:13 /usr/lib/libc.so.6 -> libc-2.20.so* So libc.so.6 actually points to the current libc version, and when I update ...


0

I finally could use RxTx library thanks to the (64 bits) librxtxSerial.so driver found at http://jlog.org/rxtx-lin.html . Before that I was getting below error, probably due to a bad librxtxSerial.so file (32 bit version or bad 64bits file?). # # A fatal error has been detected by the Java Runtime Environment: # # SIGSEGV (0xb) at pc=0x00007fb9b0249462, ...


0

I to am using Arch but haven't found any references to this same crash other than "updating the package" there is no "update for libxul.so" precisely, but some of the other error messages when trying to launch firefox from cli were helpful - I had to update "icu" as someone already mentioned, but Firefox still wouldn't launch but new error message pointed to ...


0

I did not want to mess up too much with the libraries, therefore I tried the suggestion of @john-wh-smith. Version 0.8 works perfectly with the old version of the C library (concretely for this specific case I used skype-call-recorder-ubuntu_0.8_amd64.deb). Thanks everyone!


0

You need to add the debian experimental repository to your /etc/sources.list from there you need to download and install glibc 2.17, this can be a bad idea if you don't know what you're doing though as running unstable software can be dangerous, so be weary.



Top 50 recent answers are included