How to recover libc.so.6 file if it's deleted accidentally?
Linux - DistributionsThis forum is for Distribution specific questions.
Red Hat, Slackware, Debian, Novell, LFS, Mandriva, Ubuntu, Fedora - the list goes on and on...
Note: An (*) indicates there is no official participation from that distribution here at LQ.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Hello and welcome to LQ, hope you like it here.
Please fill in your user profile so we know which distro you use.
There is no way to safely recover a complete file for usage on journalling filesystems. Easiest way would be to reinstall the package. Else check your package manager to see which version you need and download then extract the file. You're looking for Glibc.
I found that the file is actually not deleted but the symbolic link for libc.so.6 has been modified. I tried to run 'ln' command but it shows 'Segmentation Fault'. Other commands also generates segmentation fault.
Any idea how to put back the correct symbolic link?
First find the exact glibc rpm package that was installed:
rpm -q --info glibc. If you are running the 64 bit version, then you may need a glibc-32bit package instead.
Since glibc is already installed, you can force install it. "sudo rpm -I --force glibc-<version>.rpm"
If one link was deleted, maybe more of them where.
There is an rpm command option (-V) to verify packages which can tell you if you are missing files.
rpm -V glibc
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.