This error message typically occurs when attempting to install DaVinci Resolve on Linux distributions like Ubuntu 24.04 Linux Mint 22
. The installer checks for specific legacy library names that have been replaced or renamed in newer system versions. Linux Mint Immediate Solution: Core Command
To install the required libraries (or their modern equivalents), run the following command in your terminal:
sudo apt update && sudo apt install libapr1 libaprutil1 libasound2t64 libglib2.0- Use code with caution. Copied to clipboard Note: On newer versions of Ubuntu/Mint, libasound2 is replaced by libasound2t64 Linux Mint Detailed Troubleshooting Guide 1. Handling the "No Installation Candidate" Error
If you receive an error stating a package has "no installation candidate," it is usually because the installer is looking for a legacy name. Use these modern alternatives based on recent Blackmagic Forum discussions: libasound2 right arrow libasound2t64 right arrow libapr1t64 (if the standard name fails). libglib2.0-0 right arrow libglib2.0-0t64 Linux Mint 2. Bypassing the Installer Check
Even after installing the correct libraries, the DaVinci Resolve installer may continue to report them as missing because it cannot find the exact legacy filenames. You can force the installation by skipping the package check: Blackmagic Forum
sudo SKIP_PACKAGE_CHECK=1 ./DaVinci_Resolve_Studio_19.0_Linux.run Use code with caution. Copied to clipboard (Replace the filename with your specific version) 3. Common Post-Installation Fixes
If the application fails to launch after installation due to "symbol lookup errors," you may need to move conflicting internal libraries so the software uses your system's newer versions: Linux Mint
libapr1 libaprutil1 libasound2 libglib2.0-0 - Linux Mint Forums
This error message typically occurs when installing DaVinci Resolve on modern Linux distributions like Ubuntu 24.04 or Linux Mint 22. The installer fails because it looks for specific package names that have been renamed or replaced in newer operating system versions. Quick Fix (Command)
To bypass the check and force the installation, run the installer from your terminal with the following environment variable:
sudo SKIP_PACKAGE_CHECK=1 ./DaVinci_Resolve_Installer_Name.run Use code with caution. Copied to clipboard
(Replace DaVinci_Resolve_Installer_Name.run with your actual file name). Detailed Package Status Report
The "missing" packages are often already present on your system under slightly different names due to the t64 transition (a shift in how Linux handles 64-bit time values). Requested Package Modern Equivalent / Status libapr1 libapr1t64 Apache Portable Runtime library libaprutil1 libaprutil1t64 Utilities for the APR library libasound2 libasound2t64 Advanced Linux Sound Architecture (ALSA) libglib2.0-0 libglib2.0-0t64 Core utility library for C (GLib) Step-by-Step Resolution
1. Install Modern EquivalentsEnsure you have the latest versions of these libraries installed via the terminal:
sudo apt update sudo apt install libapr1t64 libaprutil1t64 libasound2t64 libglib2.0-0t64 Use code with caution. Copied to clipboard
Note: If your system is older (e.g., Ubuntu 22.04), the original names without "t64" will still work.
2. Address the libasound2 "Virtual Package" ErrorOn newer systems, libasound2 is a "virtual package" and cannot be installed directly. If the installer still complains, users often find that installing the ALSA development files helps: sudo apt install libasound2-dev Use code with caution. Copied to clipboard
3. Bypass Outdated Installer ChecksBecause the DaVinci Resolve installer uses a hardcoded list of package names, it will not recognize the t64 versions even if they are installed. Using the SKIP_PACKAGE_CHECK=1 flag mentioned above is the standard workaround recommended by community experts at Ask Ubuntu and the Blackmagic Forums.
4. Post-Installation Launch IssuesIf the software installs but fails to open, you may need to move conflicting libraries bundled with Resolve so it uses your system's newer versions: Missing Packages on Linux install - Blackmagic Forum
Please install the following missing packages: libapr1 libaprutil1 libasound2 libglib2.0-0. trying to install libapr1 for example, Blackmagic Forum How to install and set up DaVinci Resolve in Ubuntu 24.04
In the heart of a bustling tech city, there existed a quaint little café known as "The Byte-Sized Brew." This wasn't just any café; it was a haven for programmers, developers, and anyone with a passion for technology. The walls were adorned with vintage computers, and the tables were named after famous algorithms. It was here that our story begins.
Our protagonist, a bright and ambitious young programmer named Alex, was on a mission. Alex had been working on an exciting new project, a home automation system that integrated various smart devices. However, Alex's system was built on a Linux-based platform, and he was encountering a significant roadblock. His system was crying out for a set of essential packages: libapr1, libaprutil1, libasound2, and libglib2.0.
Determined to get his project back on track, Alex set out on an adventure to install these missing packages. His journey began at the local software repository, where he hoped to find the necessary files. However, the repository's search function was as elusive as a ghost, and Alex found himself lost in a maze of terminal commands and error messages.
Just as Alex was about to give up, a wise old programmer named Sam walked into the café. Sam was known for his vast knowledge of Linux and his ability to solve even the most perplexing package dependency issues. Alex approached Sam and explained his predicament.
Sam listened attentively, nodding his head from time to time, and then began to type away on his laptop. "My young friend," Sam said with a smile, "the solution lies in understanding the dependencies and using the right commands."
With a few swift keystrokes, Sam conjured up the solution:
sudo apt-get update
sudo apt-get install libapr1 libaprutil1 libasound2 libglib2.0
As the packages began to download and install, Sam explained to Alex the role of each package. libapr1 and libaprutil1 were crucial for Apache Portable Runtime, providing essential functions for Alex's system to interact with various resources. libasound2 was vital for sound support, allowing Alex's home automation system to produce alerts and notifications. Lastly, libglib2.0 was a core library for GNOME, providing a wide range of functionalities that many applications depended on.
As the installation completed, Alex's system roared back to life. His home automation project was once again on track, thanks to the successful installation of the missing packages.
Alex was overjoyed and thanked Sam for his guidance. From that day on, Alex visited Sam often at "The Byte-Sized Brew," learning more about the intricacies of programming and the adventures that awaited in the world of code.
And so, the legend of Sam, the wise package installer, spread throughout the tech community, a reminder that even in the face of error messages and dependency hell, help and guidance were always just a terminal command away. This error message typically occurs when attempting to
To install these missing packages—often required for software like DaVinci Resolve on Linux—you can use the standard package manager (apt). Direct Installation Command
Open your terminal and run the following command to install the primary packages:
sudo apt update && sudo apt install libapr1 libaprutil1 libasound2 libglib2.0-0 Use code with caution. Copied to clipboard
Troubleshooting for Modern Distributions (e.g., Ubuntu 24.04+)
If you are using a newer Linux distribution, some of these package names have changed due to the "t64" transition. If the command above fails with "package not found," try this updated version:
sudo apt install libapr1t64 libaprutil1t64 libasound2t64 libglib2.0-0t64 Use code with caution. Copied to clipboard
Why this happens: Newer versions of Ubuntu (24.04 and later) and Linux Mint have renamed these libraries to include "t64" to handle 64-bit time values.
Virtual Packages: libasound2 is sometimes a "virtual package." If apt asks you to choose one, explicitly select libasound2t64. Bypassing Installer Checks
If you have installed the packages but your software installer (like the DaVinci Resolve .run file) still claims they are missing, you can bypass the check by running the installer with a specific environment variable: sudo SKIP_PACKAGE_CHECK=1 ./your_installer_name.run Use code with caution. Copied to clipboard Summary of Package Roles libapr1: Apache Portable Runtime library. libaprutil1: Apache Portable Runtime Utility library.
libasound2: Shared library for ALSA (Advanced Linux Sound Architecture) applications.
libglib2.0-0: Core library for C routines used by GNOME and GTK+.
For further assistance, you can check community discussions on the Blackmagic Forum or Ask Ubuntu.
Are you installing DaVinci Resolve, or is this for a different application? How to install and set up DaVinci Resolve in Ubuntu 24.04
How to Fix "Please install the following missing packages: libapr1 libaprutil1 libasound2 libglib2.0-0"
If you are trying to run a new application—often a web browser like Chrome, a communication tool like Discord, or a game—and you're met with a terminal error demanding libapr1, libaprutil1, libasound2, and libglib2.0-0, you are dealing with missing shared libraries.
These packages are "dependencies," meaning the software you're trying to use relies on these pre-existing blocks of code to handle audio, system memory, and basic operating system functions.
Here is the quick fix to get your software running on Ubuntu, Debian, Linux Mint, and other Debian-based systems. The Quick Fix: One Command to Rule Them All
Open your terminal (Ctrl+Alt+T) and paste the following command. This combines all the requested packages into a single installation string:
sudo apt update && sudo apt install -y libapr1 libaprutil1 libasound2 libglib2.0-0 Use code with caution. What these packages actually do:
libapr1 / libaprutil1: The Apache Portable Runtime. It helps software handle system tasks (like memory allocation) in a way that works across different types of hardware.
libasound2: The Advanced Linux Sound Architecture (ALSA) library. This is required for your application to produce sound.
libglib2.0-0: A low-level core library that helps apps "talk" to the operating system. Without this, most graphical apps won't even start. Troubleshooting Common Issues 1. "Unable to locate package"
If you see an error saying a package couldn't be found, it’s usually because your package list is out of date. Always run sudo apt update first. If it still fails, ensure you haven't made a typo (e.g., writing libglib200 instead of libglib2.0-0). 2. Dependency Hell (Broken Packages)
If the installation fails due to "unmet dependencies," try running the "fix-broken" command: sudo apt --fix-broken install Use code with caution.
This tells Linux to look at everything you've tried to install and automatically go find the missing pieces required to make them work. 3. Still Getting the Error After Installing?
If you installed the packages but the app still complains, you might be on a 64-bit system trying to run a 32-bit application. In this case, you need the :i386 versions:
sudo dpkg --add-architecture i386 sudo apt update sudo apt install libapr1:i386 libaprutil1:i386 libasound2:i386 libglib2.0-0:i386 Use code with caution. Why did this happen?
Most modern software comes in .deb packages that automatically install their dependencies. However, if you are running a standalone binary (like a .sh file or a portable app), the system doesn't always know it needs to go grab these libraries for you.
By manually installing these four libraries, you are providing the "hooks" the application needs to interact with your speakers, your processor, and your screen.
Are you seeing this error while trying to install a specific app like Discord or Chrome? As the packages began to download and install,
If you are seeing the error "Please install the following missing packages: libapr1 libaprutil1 libasound2 libglib2.0-0 you are likely trying to install DaVinci Resolve on a Linux distribution like Ubuntu 24.04 Linux Mint 22
. This happens because the installer looks for specific library names that have changed in newer versions of Linux. Here is how to fix this: 1. Install Modern Alternatives
In newer versions of Ubuntu and Mint, these packages have been renamed (often ending in
) or replaced. Run the following command to install the current compatible versions:
sudo apt update && sudo apt install libapr1t64 libaprutil1t64 libasound2t64 libglib2.0- t64 libxcb-cursor0 Use code with caution. Copied to clipboard 2. Bypass the Package Check
Even after installing these, the DaVinci Resolve installer might still complain because it is hard-coded to look for the
old names. You can force the installer to skip this check using an environment variable: Open your terminal in the folder where the installer is located. Make the file executable: chmod +x DaVinci_Resolve_19.0_Linux.run Run the installer with the skip flag: sudo SKIP_PACKAGE_CHECK=1 ./DaVinci_Resolve_19.0_Linux.run Why is this happening?
View topic - Missing Packages on Linux install - Blackmagic Forum
This error message typically appears when you are trying to install DaVinci Resolve on a Debian-based Linux distribution (like Linux Mint
). The installer cannot find the exact package names it expects.
To resolve this, follow these steps to install the modern equivalents of those packages and then bypass the installer's check. 1. Install the Modern Packages
Newer versions of Linux (like Ubuntu 24.04) have updated these library names with a
suffix. Use the following command to install the required dependencies: Linux Mint
sudo apt update sudo apt install libapr1t64 libaprutil1t64 libasound2t64 libglib2.0- Use code with caution. Copied to clipboard
Note: If you are on an older version of Linux, try the original names provided by Ubuntu Documentation
sudo apt install libapr1 libaprutil1 libasound2 libglib2.0-0 2. Bypass the Package Check
Even after installing the libraries, the DaVinci Resolve installer might still claim they are missing because it is hard-coded to look for the exact old names. You can force the installer to run by setting a "skip" flag in your terminal: Open your terminal in the folder where the installer is located.
Run the installer with the skip command (replace the filename with your actual version): sudo SKIP_PACKAGE_CHECK=1 ./DaVinci_Resolve_19.0_Linux.run Use code with caution. Copied to clipboard 3. Fixing Launch Issues (If It Won't Open)
If the program installs but fails to open, it is often due to a conflict with internal libraries. A common fix is to move or rename certain files in the Resolve installation directory so it uses your system's newer versions instead: Linux Mint
cd /opt/resolve/libs sudo mkdir disabled-libraries sudo mv libgio* libgmodule* libglib* disabled-libraries Use code with caution. Copied to clipboard
For more specific troubleshooting tailored to your Linux setup, community discussions on Linux Mint Forums Blackmagic Design Forums provide deep-dive solutions for various versions. Linux distribution
and version (e.g., Ubuntu 24.04, Mint 22) are you currently using? DaVinci Resolve missing Packages - Linux Mint Forums
Subject: Action Required: Installation of Missing Dependencies
Body: Hello,
To proceed with the installation/configuration, please ensure the following missing packages are installed on the target system:
These libraries are required dependencies. Once installed, please retry the operation.
Best regards,
[Your Name]
Problem: The software is looking for an exact filename like libglib200.so (with no dot), but your system has libglib-2.0.so.0.
Solution – Create a symbolic link (use cautiously): Option 2: Formal Email or Support Ticket Subject:
# Find your actual glib file
find /usr/lib -name "libglib*.so*"
# Example output: /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0.6600.8
For other distributions
Fedora / RHEL / CentOS:
sudo dnf install apr apr-util alsa-lib glib2
Arch Linux:
sudo pacman -S apr apr-util alsa-lib glib2
openSUSE:
sudo zypper install libapr1 libapr-util1 alsa-lib glib2
This error message is a common hurdle when installing DaVinci Resolve on modern Linux distributions like Ubuntu 24.04 or Linux Mint 22. The installer is often looking for specific legacy package names that have been updated in newer systems. Step 1: Attempt Manual Installation
First, try to install the standard versions or their modern equivalents (t64 versions) through the terminal. Use the following command:
sudo apt update && sudo apt install libapr1 libaprutil1 libasound2t64 libglib2.0-0 Use code with caution. Copied to clipboard
Note for Ubuntu 24.04+: The package libasound2 has been replaced by libasound2t64. If the command above fails for libasound2, ensure you use the t64 suffix.
Development Headers: If you are compiling or the above doesn't work, try installing the development versions: sudo apt install libapr1-dev libaprutil1-dev libasound2-dev libglib2.0-dev. Step 2: Skip the Package Check (Most Reliable Fix)
Even if these packages are installed, the DaVinci Resolve installer may fail to recognize them because it specifically checks for the "old" names. You can bypass this check by running the installer with a specific environment variable:
Open your terminal in the folder containing your .run installer.
Make the file executable: chmod +x DaVinci_Resolve_Studio_19.0_Linux.run. Run the installer with the skip flag:
sudo SKIP_PACKAGE_CHECK=1 ./DaVinci_Resolve_Studio_19.0_Linux.run Use code with caution. Copied to clipboard (Replace the filename with your specific version). Step 3: Troubleshooting Launch Issues
If the program installs but won't open, it is likely due to library conflicts within Resolve's own folders. A common fix is to move out conflicting libraries so the system uses your native ones: Navigate to the library folder: cd /opt/resolve/libs Create a backup folder: sudo mkdir disabled-libraries Move the conflicting GLib libraries: sudo mv libglib-2.0.so* disabled-libraries/ sudo mv libgio-2.0.so* disabled-libraries/ sudo mv libgmodule-2.0.so* disabled-libraries/ Summary of Package Names Missing Package Modern/Alternative Name (if needed) libapr1 libapr1t64 libaprutil1 libaprutil1t64 libasound2 libasound2t64 libglib2.0-0 libglib2.0-0t64 Missing Packages on Linux install - Blackmagic Forum
Please install the following missing packages: libapr1 libaprutil1 libasound2 libglib2.0-0. trying to install libapr1 for example, Blackmagic Forum
libapr1 libaprutil1 libasound2 libglib2.0-0 - Linux Mint Forums
To resolve the "missing packages" error during the installation of software like DaVinci Resolve on Linux, you must install the specific shared libraries and, in some cases, bypass the installer's rigid package checks. 1. Update and Install Packages
The exact package names can vary depending on your Linux distribution's version (e.g., Ubuntu 24.04 uses
suffixes for many libraries). Run the following command in your terminal to cover the required dependencies: For Ubuntu 22.04 and older:
sudo apt update && sudo apt install libapr1 libaprutil1 libasound2 libglib2.0-0 For Ubuntu 24.04 and newer:
sudo apt update && sudo apt install libapr1t64 libaprutil1t64 libasound2t64 libglib2.0-0t64 2. Bypass Installer Package Checks
If the installer continues to report missing packages even after they are installed, it is likely because it is searching for legacy package names. You can bypass this check by setting an environment variable before running the installer: Make the installer executable: chmod +x DaVinci_Resolve_Installer.run Run the installer with the skip flag: sudo SKIP_PACKAGE_CHECK=1 ./DaVinci_Resolve_Installer.run 3. Resolving Runtime Library Conflicts
After a successful installation, the application may still fail to launch due to conflicts between system libraries and the bundled libraries located in /opt/resolve/libs . Common fixes include: Move Bundled Libraries
: If you see "symbol lookup" errors, try moving the bundled glib libraries so the app uses system versions instead: sudo mkdir /opt/resolve/libs/disabled-libraries
sudo mv /opt/resolve/libs/libglib-2.0.so* /opt/resolve/libs/disabled-libraries/
sudo mv /opt/resolve/libs/libgio-2.0.so* /opt/resolve/libs/disabled-libraries/
sudo mv /opt/resolve/libs/libgmodule-2.0.so* /opt/resolve/libs/disabled-libraries/ Linux Mint What specific Linux distribution and version
are you currently running? knowing this will help determine if you need the versions of these libraries. DaVinci Resolve missing Packages - Linux Mint Forums
Understanding the Error: What Are These Packages?
Before diving into the commands, let's break down what each library does. Understanding this will help you diagnose similar errors in the future.
2. Update package lists
sudo apt update
Introduction
Linux users frequently encounter dependency-related errors when installing software, especially when using package managers like apt, yum, or dnf. A common but confusing message is:
“Please install the following missing packages: libapr1 libaprutil1 libasound2 libglib200”
This essay explains what these packages are, why the error occurs, and how to resolve it systematically.
Scenario B: You are trying to install a specific .deb file
If you downloaded a .deb file and are running sudo dpkg -i package.deb, and it threw these errors:
- Run the install command again, but fix the broken dependencies automatically:
sudo dpkg -i your_package.deb
sudo apt-get install -f
The -f (fix-broken) command tells apt to search the official repositories for libapr1, libaprutil1, and libasound2 and install them for you.
Troubleshooting & Solutions