Error While Loading Shared Cannot Open Shared Object No Such File or Directory

Got That Weird Linux Library Error? Here’s How to Fix It (Seriously, It’s Easy)

If you’ve ever worked on a Linux server or written some code, you’ve probably seen this annoying error pop up:

error while loading shared libraries: [library_name].so: cannot open shared object file: No such file or directory

Yeah, it looks scary. Like something exploded. But honestly? It’s one of the easiest problems to fix. I’ll walk you through exactly how to solve it in the next five minutes.

The Quick Fix (Copy & Paste)

If you just want to get this working right now, run these commands one after another:

Step 1: Find the missing library

ldd /path/to/your/program

Look for anything that says “not found” — that’s your culprit.

Step 2: Figure out which package has it

# If you're on Ubuntu/Debian:
apt-file search libname.so
# If you're on CentOS/RHEL:
yum whatprovides libname.so

Step 3: Install the package

sudo apt install [package_name]

(Or yum install if you’re on RedHat/CentOS)

Step 4: Tell your system about the new library

sudo ldconfig

Done. Try running your program again. It should work now.

What’s Actually Happening Here?

Okay, so why did this error happen in the first place? Let me explain without making your brain hurt.

In Linux, programs don’t carry around all their code bundled into one giant file. That would be inefficient. Instead, they use something called Shared Objects (those .so files) — think of them as little building blocks that multiple programs can use.

Your program went looking for one of these building blocks, couldn’t find it anywhere, and threw its hands up in frustration.

This happens for three main reasons:

1. The library just isn’t installed on your system. You need to install it from your package manager (apt, yum, etc.).
2. The library exists, but it’s hiding in a weird folder. Maybe you installed it manually somewhere like /opt/ or /usr/local/lib, and your system doesn’t know to look there.
3. Architecture mismatch. You’re trying to run a 32-bit program on a 64-bit system, but you don’t have the 32-bit libraries installed. This is common with older software.

The Most Common Missing Libraries (Copy These If You Need Them)

Here are the libraries that cause this error most often:

Just copy the command for your system and paste it in. Easy.

What If The Library Is Already Installed But Linux Can’t Find It?

Sometimes you download a library manually or install some custom software in a non-standard location. Your system looks in all the usual places (/usr/lib, /lib, etc.) but can’t find it.

You have two options:

Option 1: Quick Temporary Fix (Just For This Run)

You can tell your program exactly where to look by setting an environment variable:

export LD_LIBRARY_PATH=/path/to/custom/lib:$LD_LIBRARY_PATH
./your_program

This works great if you only need it to run once or twice. But if you close your terminal and come back, you’ll have to do it again.

Option 2: Permanent Fix (Do It Once, Forget About It)

If you want your system to always know where the library is:

Step 1: Create a new configuration file

sudo nano /etc/ld.so.conf.d/custom-libs.conf

Step 2: Type the path to your library folder (for example: /opt/myapp/libs)

Step 3: Save the file and run

sudo ldconfig

Done. Now your system will always find that library, even after you restart.

Pro Tips (So You Don’t Have To Do This Again)

• Always use your package manager (apt, yum, dnf, pacman) to install libraries. Don’t download random .so files from the internet. It’s a security risk and causes way more problems than it solves.
• Keep your system updated. Running sudo apt update && sudo apt upgrade regularly prevents a lot of these issues from happening in the first place.
• Save your LD_LIBRARY_PATH changes. If you use Option 1 a lot, add the export line to your ~/.bashrc file so it runs automatically every time you open a terminal.

Still Stuck?

If you’ve tried all this and it’s still not working, try:

1. Double-check the library path in step 1. Make sure you’re reading the error correctly.
2. Run ldconfig -p | grep libname to see ALL the versions of that library installed on your system.
3. Check if you need to install the 32-bit version (add :i386 at the end on Ubuntu).

That should cover 99% of cases. Good luck!

Follow Me : Facebook | Youtube | Linkedin | Pinterest