Kodi 21.3 (Omega) runs beautifully on Fedora 43 and 42. This guide walks through installing the media center on both releases using RPM Fusion, launching it for the first time, and adding video sources so the library actually has something to show.
Fedora does not ship Kodi in its main repositories because the project pulls in codecs and libraries that fail Fedora’s free-software policy. The fix is the RPM Fusion repository, which is maintained by the community and is the standard way to get Kodi, VLC, and most multimedia packages on Fedora. Once RPM Fusion is enabled, the actual install is a single dnf command.
Tested April 2026 on Fedora 43 (kernel 6.17.1) and Fedora 42 (kernel 6.14.0) with Kodi 21.3 from rpmfusion-free-updates.
What you need before starting
Kodi is a desktop media center, so run it on a Fedora system that already has a graphical session (Workstation, a spin like KDE or XFCE, or a Silverblue image). The install itself is identical across all Fedora editions because everything goes through RPM Fusion.
- Fedora 43 or Fedora 42 with a graphical desktop
- A user account with sudo privileges
- Internet access to reach the Fedora and RPM Fusion mirrors (roughly 230 MB of downloads)
- About 500 MB of free disk space for Kodi and its dependencies
- Tested on: Kodi 21.3, Fedora 43 Workstation, Fedora 42 Workstation
Step 1: Enable the RPM Fusion repositories
RPM Fusion ships two separate channels. The free channel covers open-source software that Fedora cannot distribute because of patents or licensing friction (Kodi, x264, vaapi drivers for older GPUs). The nonfree channel covers proprietary bits such as the NVIDIA driver and certain codecs. Kodi itself lives in free, but add-ons pulled in later often reach across into nonfree, so enable both up front.
Open a terminal and run both installers in one command. The $(rpm -E %fedora) expansion fills in your Fedora release number automatically, so the same line works on 43, 42, or any newer release:
sudo dnf install -y \
https://download1.rpmfusion.org/free/fedora/rpmfusion-free-release-$(rpm -E %fedora).noarch.rpm \
https://download1.rpmfusion.org/nonfree/fedora/rpmfusion-nonfree-release-$(rpm -E %fedora).noarch.rpmYou should see the two release RPMs install cleanly:
Package Arch Version Repository Size
Installing:
rpmfusion-free-release noarch 43-1 @commandline 5.6 KiB
rpmfusion-nonfree-release noarch 43-1 @commandline 5.8 KiB
Transaction Summary:
Installing: 2 packages
Complete!On Fedora 42 the only difference is the version string (42-1 instead of 43-1). Confirm both repositories are now registered:
dnf repolist | grep rpmfusionThe output lists four enabled repos (free, free-updates, nonfree, nonfree-updates):
rpmfusion-free RPM Fusion for Fedora 43 - Free
rpmfusion-free-updates RPM Fusion for Fedora 43 - Free - Updates
rpmfusion-nonfree RPM Fusion for Fedora 43 - Nonfree
rpmfusion-nonfree-updates RPM Fusion for Fedora 43 - Nonfree - UpdatesStep 2: Install Kodi
With RPM Fusion in place, pulling Kodi is one command. The package brings in around 210 dependencies on a clean Fedora Workstation (pipewire plugins, Mesa drivers, libva, ffmpeg libraries, and the Estuary skin), so expect a few minutes on a slow link:
sudo dnf install -y kodidnf resolves the transaction, downloads the packages, and runs the scriptlets that wire Kodi into pipewire for audio. When it finishes, the last lines look like this:
>>> Running %posttrans scriptlet: wireplumber-0:0.5.14-1.fc43.x86_64
>>> Finished %posttrans scriptlet: wireplumber-0:0.5.14-1.fc43.x86_64
Complete!Verify the install and check the version you actually got:
kodi --versionOn both Fedora 43 and Fedora 42 you should see the same upstream release, Kodi 21.3 (Omega):
Kodi Media Center 21.3 (21.3.0) Git:20251102-nogitfound
Copyright (C) 2005-2025 Team Kodi - http://kodi.tvIf you want to know exactly which repository provided the package, ask dnf directly:
dnf info kodi | grep -E 'Name|Version|Release|From'The output confirms Kodi came from the free updates channel, not the base Fedora repos:
Name : kodi
Version : 21.3
Release : 2.fc43
Installed size : 71.4 MiB
From repository : rpmfusion-free-updatesStep 3: Launch Kodi for the first time
The RPM Fusion package installs a desktop entry, so Kodi shows up in the GNOME Activities overview (or the equivalent menu on KDE, XFCE, and other spins). Search for “Kodi” and click the icon, or launch it from the terminal with a plain kodi command.
First startup takes a few seconds while Kodi scans for add-ons and builds the initial database. Once it settles, you land on the Estuary home screen with Movies selected in the sidebar and an empty library dialog in the middle:
The left sidebar is the main menu. Everything Kodi does (Movies, TV Shows, Music, Pictures, Add-ons, Settings) lives there. The empty library prompt on the right is Kodi telling you it has nothing to show yet because no media sources have been added. That is the next step.
Step 4: Add your first media source
Kodi organises content by section (Movies, TV Shows, Music, Videos) and each section maintains its own list of sources. Sources can be local folders, USB drives, network shares (SMB, NFS, WebDAV), or add-ons that stream from online services. For this walkthrough, add a generic Videos source so you can see the flow.
From the home screen, click Enter files section on the Movies panel. Kodi drops you into the Videos view, which starts empty except for a single Add videos… entry:
Pressing Backspace (or clicking the back arrow) moves up one level and shows the three content types Kodi can manage under Videos: Files, Playlists, and Video add-ons. Pick Files when you want to point Kodi at a folder full of your own media:
Click Add videos…, then Browse, and navigate to the folder that holds your media. For a local folder, pick Root filesystem and drill down to something like /home/yourname/Videos. For a network share, select Add network location and fill in the SMB or NFS path. Give the source a name when prompted, then tell Kodi what kind of content it contains (movies, TV shows, or music videos) so the scraper can fetch artwork and metadata.
Step 5: Explore the add-ons browser
Kodi’s real power is its add-on ecosystem. The official repository ships hundreds of free add-ons for streaming services, podcasts, weather, PVR backends, skins, and subtitle providers. From the Videos view, selecting Video add-ons opens a browser that lists what you already have installed and offers a shortcut to grab more:
To install something official, navigate to Add-ons in the main sidebar, choose Install from repository, pick Kodi Add-on repository, and browse categories like Video add-ons, Music add-ons, or Subtitles. Popular picks include YouTube, Twitch, Radio, and the OpenSubtitles.org subtitle fetcher. Each add-on installs with one click and appears under its parent category immediately.
Stick with the official repository unless you know exactly what a third-party source is doing. Unofficial repos are a common way people end up with broken add-ons or, worse, add-ons that scrape piracy sources and get the whole Kodi project blamed for it. There is plenty of legitimate content in the official repo.
Enable hardware video acceleration (optional)
On a bare Fedora install, Kodi plays video on the CPU. That is fine for 720p but chokes on 4K HEVC. To let your GPU do the decoding, install the VA-API drivers that match your hardware. Intel and AMD GPUs use Mesa, and both drivers live in the Fedora main repo:
sudo dnf install -y libva-utils mesa-va-drivers-freeworldThe freeworld variant comes from RPM Fusion and adds the proprietary codec paths (H.264, HEVC, VC-1) that Fedora strips out of its own mesa-va-drivers build. Confirm VA-API can see your GPU:
vainfo 2>&1 | grep -E 'Driver version|VAProfile'NVIDIA users need the proprietary driver plus nvidia-vaapi-driver from RPM Fusion nonfree. After rebooting, flip Kodi into hardware mode under Settings → Player → Videos → Allow hardware acceleration (VAAPI). Set the Settings level to “Advanced” at the bottom of the settings window if the option does not show up.
Fedora 43 vs Fedora 42 differences
The install steps above are identical on both releases because the Kodi package in RPM Fusion is rebuilt against each Fedora version with the same 21.3 source. What does change is the wider environment around Kodi:
| Item | Fedora 43 | Fedora 42 |
|---|---|---|
| Kodi package | kodi-21.3-2.fc43 | kodi-21.3-2.fc42 |
| Source repo | rpmfusion-free-updates | rpmfusion-free-updates |
| Default kernel | 6.17.x | 6.14.x |
| GNOME version | 49 (Wayland only) | 48 (Wayland default, X11 still available) |
| Mesa / Xorg | Mesa 25.3, no Xorg session in GNOME | Mesa 25.1, Xorg session still present |
| RPM version | RPM 6.0 (new signing) | RPM 4.x |
The GNOME shift matters if you run Kodi on a machine where you expected to fall back to an Xorg session. On Fedora 43 Workstation, GNOME is Wayland only. Kodi handles Wayland fine because upstream ships Wayland, X11, and GBM builds, and RPM Fusion packages the X11 build which runs transparently under Xwayland. If you want a pure Wayland binary, install kodi-wayland instead of the default kodi package. For kiosk-style setups without a compositor at all, kodi-gbm talks directly to DRM/KMS.
Troubleshooting common issues
Error: “No suitable GL device available”
Kodi refuses to launch on some VMs and minimal spins because no OpenGL driver is present. The quick fix is to install the software rasteriser so Kodi has at least a CPU fallback:
sudo dnf install -y mesa-dri-drivers mesa-libEGL
LIBGL_ALWAYS_SOFTWARE=1 kodiOn physical hardware this should never be needed. If it is, your GPU driver is not loading, which is a separate issue to chase in dmesg.
libva error: vaGetDriverNames() failed
This message is harmless unless you actually need hardware acceleration. It means libva could not find a driver for the current display, often because you are on a VM or a headless server. To silence it, install the Freeworld drivers from the section above, or accept that Kodi will fall back to software decoding and move on.
Kodi has no sound on Fedora 43
Fedora is pipewire-first. The Kodi package pulls in pipewire-pulseaudio as a compatibility layer so it can talk to the PulseAudio socket pipewire provides. If audio is silent, check that the pipewire session is running:
systemctl --user status pipewire pipewire-pulse wireplumberAll three services should be active (running). In Kodi, open Settings → System → Audio and make sure the output device matches your real hardware (HDMI, analog, USB). PulseAudio output via the PipeWire bridge is the right choice in almost every case.
Autostart Kodi at login (optional)
For a living-room machine that should behave like a media appliance, drop a user-level systemd unit that launches Kodi after the graphical session starts. Create the unit file:
mkdir -p ~/.config/systemd/user
vi ~/.config/systemd/user/kodi.servicePaste the following content and save:
[Unit]
Description=Kodi Media Center
After=graphical-session.target
PartOf=graphical-session.target
[Service]
ExecStart=/usr/bin/kodi --standalone
Restart=on-failure
RestartSec=5
[Install]
WantedBy=graphical-session.targetEnable the unit so it starts on the next login:
systemctl --user daemon-reload
systemctl --user enable kodi.serviceFor a truly unattended setup, also enable GDM autologin for the kodi user by adding AutomaticLoginEnable=true and AutomaticLogin=kodi to the [daemon] section of /etc/gdm/custom.conf. On a headless box without a desktop at all, install kodi-gbm and let systemd run it against DRM directly. That is the setup Team Kodi recommends for dedicated hardware.
Where to go next
Kodi is now installed, launched, and ready to index your media. The First Time User page on the Kodi wiki is worth a read for the details of content scanning, skins, and remote control apps. If you prefer a server-oriented media stack that streams to browsers and phones, Plex Media Server on Ubuntu or Plex on Debian are the usual alternatives. For a containerised media host, Emby in Docker covers that angle, and securing a Plex or Kodi server with Let’s Encrypt walks through putting HTTPS in front of a remote instance. While you are updating Fedora packages, installing Go on Fedora 43 is another useful base for building your own tools.
The second Google result
fosslinux.com/708/how-to-install-kodi-media-center-on-fedora-24.htm
appears to have done a bad copy and paste of this article.
Thank you very much.
Welcome!