Computers Drivers and Software

glibc_2.34 not found Error in Ubuntu

The error glibc_2.34 not found indicates that the GNU C Library (glibc) version required by an application is not present on your Ubuntu system. This situation often arises when you’re running an application compiled on a system with a newer version of glibc than what’s available on your system.

To resolve this issue, you have a few options:

1. Upgrade Your Ubuntu Version

If you’re running an older version of Ubuntu, upgrading to a newer release might provide the needed glibc version. Ubuntu releases typically come with specific versions of glibc. Ensure that the Ubuntu version you upgrade to includes glibc 2.34 or later.

To upgrade Ubuntu, you can use the do-release-upgrade command. Remember, upgrading your OS is a significant change, so back up important data before proceeding.

2. Install the Required glibc Version Manually

Manually installing a specific version of glibc is generally not recommended because it can lead to system instability. glibc is a critical component, and different parts of the system depend on a specific version. However, if you must have a specific version, you can compile and install it from source.

You can find the glibc versions at the GNU C Library sources page. Download the required version and follow the build and installation instructions. Be aware that this is an advanced procedure and can potentially break your system if not done correctly.

3. Use a Docker Container

If upgrading your entire system for one application isn’t feasible, consider using Docker. You can create or use a Docker container that runs a version of Ubuntu with the required glibc version. This method isolates the application and its dependencies from your system, reducing the risk of system-wide issues.

4. Compile the Application for Your Current glibc Version

If you have access to the application’s source code, recompile it on your system or a system with the same glibc version as yours. This ensures that the application is compatible with the glibc version available on your system.

5. Use a Virtual Machine

Similar to Docker, you can use a virtual machine with an appropriate version of Ubuntu that has the required glibc. This approach provides even stronger isolation than Docker but at the cost of higher resource usage.


  • Before taking any action, identify the glibc version on your system using ldd --version.
  • Be cautious with manual installations or upgrades of critical system libraries like glibc.
  • Always back up important data before making significant system changes.

The choice of solution depends on your specific circumstances, such as the importance of the application, your ability to manage system configurations, and how critical system stability is to your operations.

Leave a Reply

Your email address will not be published. Required fields are marked *