Rocky Linux keeps patent-sensitive codecs, proprietary drivers, and some multimedia tools out of its base repositories, so RPM Fusion fills a practical gap for desktop and workstation systems. To install RPM Fusion on Rocky Linux, enable the dependency repository, add EPEL, then install the RPM Fusion Free and Nonfree release packages for your Enterprise Linux major version.
The same RPM Fusion setup works on Rocky Linux 10, 9, and 8. The only release-specific difference in the core workflow is the dependency repository name: Rocky Linux 10 and 9 use CRB, while Rocky Linux 8 uses PowerTools.
Install RPM Fusion on Rocky Linux
RPM Fusion depends on EPEL, and many RPM Fusion packages also need libraries from CRB or PowerTools. Run the setup in this order so later multimedia, driver, and desktop packages can resolve their dependencies cleanly.
Update Rocky Linux Before Enabling RPM Fusion
Refresh package metadata and apply pending Rocky Linux updates before adding third-party repositories:
sudo dnf upgrade --refreshCommands that change repositories or install packages use
sudobecause they write to system package-manager paths. Run them from an account with administrator privileges.
Install the DNF Config Manager Plugin
Install the DNF plugin package that provides dnf config-manager, the helper used for CRB, PowerTools, and RPM Fusion testing repository toggles:
sudo dnf install dnf-plugins-core -yEnable CRB or PowerTools for RPM Fusion Dependencies
Enable the dependency repository that matches your Rocky Linux major version. Rocky Linux 10 and 9 use CRB:
sudo dnf config-manager --set-enabled crbRocky Linux 8 uses PowerTools instead:
sudo dnf config-manager --set-enabled powertoolsConfirm that the matching repository is enabled:
dnf repolist --enabled | grep -E '^(crb|powertools)[[:space:]]'Relevant output on Rocky Linux 10 or 9 shows CRB:
crb Rocky Linux 10 - CRB
Rocky Linux 8 shows PowerTools instead:
powertools Rocky Linux 8 - PowerTools
Install EPEL on Rocky Linux
RPM Fusion uses packages from Extra Packages for Enterprise Linux, usually shortened to EPEL. Install the EPEL release package from Rocky Linux’s Extras repository:
sudo dnf install epel-release -yVerify the EPEL repository is available before installing RPM Fusion:
dnf repolist --enabled | grep -E '^epel[[:space:]]'Rocky Linux 10 returns a line similar to this:
epel Extra Packages for Enterprise Linux 10 - x86_64
Rocky Linux does not use EPEL Next. That repository is for CentOS Stream, so ignore older Rocky Linux instructions that include
epel-next-release.
If EPEL is already configured, such as from a previous EPEL setup on Rocky Linux, keep it enabled and continue with RPM Fusion.
Install RPM Fusion Free and Nonfree Repositories
RPM Fusion publishes separate Free and Nonfree release packages. Free contains open-source packages Fedora and Enterprise Linux cannot ship for legal or policy reasons, while Nonfree contains redistributable packages with more restrictive licensing, including some driver and firmware-related packages.
The RPM Fusion configuration page is the upstream reference for current repository setup and publishes the Enterprise Linux release package URLs for this workflow.
These release RPMs are repository bootstrap packages. They install RPM Fusion repository files and signing keys; they are not a general local .rpm package installation workflow.
Install both release packages with the current EL major-version macro:
sudo dnf install --nogpgcheck \
"https://mirrors.rpmfusion.org/free/el/rpmfusion-free-release-$(rpm -E %rhel).noarch.rpm" \
"https://mirrors.rpmfusion.org/nonfree/el/rpmfusion-nonfree-release-$(rpm -E %rhel).noarch.rpm" -yThe $(rpm -E %rhel) macro expands to 10, 9, or 8, which keeps the command portable across supported Rocky Linux releases. The initial --nogpgcheck applies only to the small remote release RPM download; the release packages install RPM Fusion key files so normal package transactions can use signed RPMs afterward.
Verify the installed release packages:
rpm -q rpmfusion-free-release rpmfusion-nonfree-releaseRocky Linux 10 currently shows:
rpmfusion-free-release-10-1.noarch rpmfusion-nonfree-release-10-1.noarch
Confirm that the enabled RPM Fusion repositories are visible to DNF:
dnf repolist --enabled | grep -i rpmfusionRelevant repository lines on Rocky Linux 10 include:
rpmfusion-free-updates RPM Fusion for EL 10 - Free - Updates rpmfusion-nonfree-updates RPM Fusion for EL 10 - Nonfree - Updates
Verify RPM Fusion Packages on Rocky Linux
After the repositories are enabled, use DNF to check whether a package comes from RPM Fusion before installing it. This is more reliable than relying on old package-count claims, because the package set changes as Enterprise Linux releases move forward.
Search for RPM Fusion Packages
List a small sample of available RPM Fusion packages:
dnf --enablerepo='rpmfusion-*' list available | grep rpmfusion | head -50The command temporarily includes RPM Fusion repositories, filters the package list, and limits the sample to the first 50 matching rows. Package availability and counts change by branch and architecture, so use the output as a discovery aid, not as a complete or permanent inventory.
Check Which Repository Provides a Package
Query a package directly when you want source proof. For example, ffmpeg comes from RPM Fusion Free on supported Rocky Linux releases:
dnf repoquery --info ffmpeg | grep -E '^(Name|Version|Release|Architecture|Repository|Summary)[[:space:]]+:'Relevant output on Rocky Linux 10 includes:
Name : ffmpeg Version : 7.1.4 Release : 1.el10 Architecture : x86_64 Repository : rpmfusion-free-updates Summary : Digital VCR and streaming server
The exact ffmpeg version differs by Rocky Linux release, but the Repository line is the key detail. It tells you whether DNF will install the package from Rocky Linux, EPEL, or RPM Fusion.
If your goal is GPU support rather than codecs, use the dedicated guide to install NVIDIA drivers on Rocky Linux after RPM Fusion is available.
Install Optional RPM Fusion Components
The core Free and Nonfree repositories are enough for most users. Add optional components only when you need graphical software-center metadata, multimedia codec groups, testing packages, or tainted packages.
Add RPM Fusion Metadata to Software Centers
On desktop systems, update the core AppStream metadata so GNOME Software and KDE Discover can display RPM Fusion applications:
sudo dnf update @coreThis step helps graphical software centers. CLI-only packages still appear through normal DNF search and repoquery commands.
Install RPM Fusion Multimedia Codecs
For GStreamer-based video and audio playback, install the multimedia group from RPM Fusion and EPEL:
sudo dnf update @multimedia --setopt="install_weak_deps=False" --exclude=PackageKit-gstreamer-pluginDNF may print No match for group package for release-specific group members that are not available on your Rocky Linux version. Continue only when the transaction summary still lists the Multimedia group and does not report a dependency failure.
Enable RPM Fusion Tainted Repositories
Tainted repositories contain packages with additional patent, licensing, or redistribution concerns. Install them only when you know you need a package from those branches, such as libdvdcss from Free Tainted.
sudo dnf install rpmfusion-free-release-tainted rpmfusion-nonfree-release-tainted -yVerify the tainted repository IDs:
dnf repolist --enabled | grep -E '^rpmfusion-(free|nonfree)-tainted[[:space:]]'Rocky Linux 10 shows:
rpmfusion-free-tainted RPM Fusion for EL 10 - Free tainted rpmfusion-nonfree-tainted RPM Fusion for EL 10 - Nonfree tainted
Avoid wildcard firmware installs such as
sudo dnf install \*-firmware. Query the exact hardware or package name first so DNF does not install firmware you do not need.
Enable RPM Fusion Testing Repositories
Testing repositories provide packages before they move to the stable updates branches. Enable them only for troubleshooting or early testing, not as the default setup on production systems:
sudo dnf config-manager --set-enabled rpmfusion-free-updates-testing
sudo dnf config-manager --set-enabled rpmfusion-nonfree-updates-testingReturn to stable RPM Fusion packages by disabling the testing repositories:
sudo dnf config-manager --set-disabled rpmfusion-free-updates-testing
sudo dnf config-manager --set-disabled rpmfusion-nonfree-updates-testingRemove RPM Fusion from Rocky Linux
Removing the RPM Fusion release packages disables the repository files, but it does not automatically remove applications or codecs you installed from RPM Fusion. Those packages stay installed and stop receiving RPM Fusion updates until you re-enable the repositories or remove the packages. Check installed packages first, then remove the repository packages.
dnf list installed | grep -i rpmfusion || echo "No installed packages show RPM Fusion in the package listing"Remove whichever RPM Fusion release packages are installed:
packages=(
rpmfusion-free-release
rpmfusion-nonfree-release
rpmfusion-free-release-tainted
rpmfusion-nonfree-release-tainted
)
installed=()
for package in "${packages[@]}"; do
if rpm -q "$package" >/dev/null 2>&1; then
installed+=("$package")
fi
done
if ((${#installed[@]})); then
sudo dnf remove "${installed[@]}"
else
echo "No RPM Fusion release packages are installed"
fiConfirm that RPM Fusion repositories are no longer enabled:
dnf repolist --enabled | grep -i rpmfusion || echo "RPM Fusion repositories are disabled"If you want to remove RPM Fusion signing keys from the RPM database after removing every RPM Fusion repository, resolve the matching key packages first:
mapfile -t rpmfusion_keys < <(
rpm -q gpg-pubkey --qf '%{NAME}-%{VERSION}-%{RELEASE} %{SUMMARY}\n' |
awk 'tolower($0) ~ /rpm fusion|rpmfusion/ {print $1}'
)
if ((${#rpmfusion_keys[@]})); then
sudo rpm -e "${rpmfusion_keys[@]}"
else
echo "No RPM Fusion RPM signing keys found"
fiDo not remove RPM Fusion signing keys while any RPM Fusion repository or installed RPM Fusion package still depends on them. Key cleanup is an optional full-trust reset, not a normal package removal requirement.
Leave EPEL, CRB, or PowerTools enabled if other packages on the system use them. If you enabled one only for this RPM Fusion setup and no longer need it, disable the matching repository for your release:
Rocky Linux 10 and 9 use CRB:
sudo dnf config-manager --set-disabled crbRocky Linux 8 uses PowerTools:
sudo dnf config-manager --set-disabled powertoolsTroubleshoot RPM Fusion on Rocky Linux
dnf config-manager Command Not Found
Minimal Rocky Linux installations may not include the DNF plugin that provides config-manager. The error looks like this:
dnf: error: No such command: config-manager
Install the plugin package, then rerun the CRB or PowerTools command:
sudo dnf install dnf-plugins-core -y
dnf --versionRepository Metadata or Mirrorlist Errors
Mirror metadata can fail temporarily during release rollouts or mirror sync windows. One common shape is:
Error: Failed to download metadata for repo 'appstream': Cannot prepare internal mirrorlist: No URLs in mirrorlist
Clean cached metadata and rebuild the cache before changing repository commands:
sudo dnf clean all
sudo dnf makecache --refreshIf the same mirrorlist error continues, wait for the mirror to recover or check the Rocky Linux mirror status. Do not switch to EPEL Next or CentOS Stream repository packages on Rocky Linux.
GPG Key Prompt or Import Failure
The first package transaction from RPM Fusion may ask you to import a signing key. A normal prompt includes the key ID, user ID, fingerprint, and local key file:
Importing GPG key 0x1BC7B804: Userid : "RPM Fusion nonfree repository for EL (10) <rpmfusion-gpg-key-el10-nonfree@rpmfusion.org>" Fingerprint: 06DE E60A C32C 1F08 1BD5 47DB F447 105D 1BC7 B804 From : /etc/pki/rpm-gpg/RPM-GPG-KEY-rpmfusion-nonfree-el-10
If key import fails, import the current EL keys from the RPM Fusion mirror and retry the package transaction:
sudo rpm --import "https://download1.rpmfusion.org/free/el/RPM-GPG-KEY-rpmfusion-free-el-$(rpm -E %rhel)"
sudo rpm --import "https://download1.rpmfusion.org/nonfree/el/RPM-GPG-KEY-rpmfusion-nonfree-el-$(rpm -E %rhel)"Check for imported RPM Fusion keys:
rpm -q gpg-pubkey --qf '%{NAME}-%{VERSION}-%{RELEASE} %{SUMMARY}\n' | grep -Ei 'rpm fusion|rpmfusion'Multimedia Group Shows No Match Warnings
DNF groups can contain package names that differ between Rocky Linux 10, 9, and 8. During multimedia setup, warnings like these can appear without breaking the group transaction:
No match for group package "PackageKit-gstreamer-plugin" No match for group package "gstreamer1-libav"
Review the transaction summary. If DNF still lists the intended group and packages from rpmfusion-free-updates, continue. If DNF reports unresolved dependencies instead, confirm EPEL and CRB or PowerTools are enabled before retrying.
Conclusion
RPM Fusion is now available to DNF on Rocky Linux, with Free and Nonfree repositories ready for multimedia tools, codecs, and driver-related packages. Keep DNF performance tuning on Rocky Linux nearby if repository downloads feel slow, and use Remi RPM on Rocky Linux when PHP stacks need a separate third-party package source.
is there any chacne you can update this for rocky 10?? as it doesnt work for that
Hi Paul,
Article updated.