โ† Back to blog

๐Ÿง Things to do after installing Fedora 45

I tested these steps on Fedora 45 Workstation with Intel graphics in November 2026. The exceptions are the AMD and NVIDIA commands and the section on what is new in Fedora 45: those come from the official documentation, and I have not tested them myself.

This is the list I go through after a fresh install. Each step is short, and I explain why it is worth doing. Most steps are the same on every machine. Step 5, hardware video acceleration, is the most hardware dependent step in the guide: the right package depends on whether you have Intel, AMD, or NVIDIA graphics, so read that section carefully.

๐Ÿ”„ 1. Update the system and reboot

A fresh install is already a few weeks old. Updating first means that the rest of the guide builds on current packages, and that known bugs and security holes are fixed.

sudo dnf upgrade --refresh

--refresh forces dnf to fetch fresh repository metadata. Reboot afterwards, so the new kernel and system libraries are actually in use.

๐Ÿ“ฆ 2. Enable RPM Fusion (Free and Nonfree)

Fedora only ships software that it can distribute freely. RPM Fusion is the community repository for everything else, such as the full ffmpeg and several hardware drivers. Free contains open source software that Fedora cannot ship for legal reasons, and Nonfree contains software that is not open source.

sudo dnf install https://mirrors.rpmfusion.org/free/fedora/rpmfusion-free-release-$(rpm -E %fedora).noarch.rpm https://mirrors.rpmfusion.org/nonfree/fedora/rpmfusion-nonfree-release-$(rpm -E %fedora).noarch.rpm

$(rpm -E %fedora) expands to your Fedora version, so the command keeps working on later releases.

When you install a package directly from a web address like this, dnf warns that it skipped OpenPGP checks. That is normal for exactly this package: the release package is the one that adds the RPM Fusion repositories and their signing keys, so there is no trusted key to check it against yet. Every package you install from RPM Fusion afterwards is checked against those keys as usual.

๐ŸŽฌ 3. Switch to the full ffmpeg

Fedora ships ffmpeg-free, a build with only the codecs that are free of patents and licensing restrictions. Formats such as H.264 and HEVC are covered by patents in some countries, so Fedora leaves them out. RPM Fusion has the full ffmpeg, and dnf swap replaces one with the other in a single step:

sudo dnf swap ffmpeg-free ffmpeg --allowerasing

--allowerasing lets dnf remove ffmpeg-free and the packages that conflict with the full build. Check the result:

rpm -q ffmpeg ffmpeg-free

ffmpeg must be installed, and ffmpeg-free must report is not installed.

Note: to undo it, run the swap in the opposite order: sudo dnf swap ffmpeg ffmpeg-free --allowerasing. The order of the two package names matters. The first name is removed and the second one is installed.

๐ŸŽต 4. Install the multimedia group

The multimedia group pulls in the GStreamer plugins and the other pieces that browsers and media players use to play audio and video. RPM Fusion's multimedia guide currently recommends:

sudo dnf install @multimedia --setopt="install_weak_deps=False" --exclude=PackageKit-gstreamer-plugin

I used the shorter form, which installs the same group with Fedora's default settings:

sudo dnf group install multimedia

Older versions of RPM Fusion's guide used sudo dnf update @multimedia and sudo dnf update @sound-and-video. The current guide no longer mentions them, so I follow the command above.

If you look at sudo dnf history info afterwards, you will see lines marked Reason Change. That only means that packages you already had are now marked as part of the group. Nothing is installed or removed by those lines.

๐ŸŽž๏ธ 5. Hardware video acceleration

Without hardware acceleration, video is decoded by the processor, which costs battery and makes the fan spin. With it, the graphics chip does the work. This is where Intel, AMD, and NVIDIA differ the most.

First, find out which graphics chip the machine uses:

lspci | grep -Ei 'vga|3d|display'

Laptops with both integrated and dedicated graphics, for example Intel plus NVIDIA, normally play video on the integrated chip. That is the one to install the driver for.

Chip Package Repository How to check
Intel, Broadwell and newer intel-media-driver RPM Fusion Nonfree vainfo shows Intel iHD driver
Intel, older than Broadwell libva-intel-driver RPM Fusion Free vainfo shows the i965 driver
AMD mesa-va-drivers-freeworld RPM Fusion Free vainfo shows Mesa Gallium driver and AMD Radeon
NVIDIA libva-nvidia-driver RPM Fusion vainfo lists the NVIDIA driver

Intel (tested)

intel-media-driver is not open source and comes from RPM Fusion Nonfree. Intel's own documentation lists support from Broadwell onwards, including Coffee Lake and the later generations. For older chips, RPM Fusion points to libva-intel-driver from RPM Fusion Free. libva-utils provides the vainfo test tool.

sudo dnf install intel-media-driver libva-utils
vainfo

The output should mention Intel iHD driver and list profiles such as VAProfileH264 and VAProfileHEVC. Older chips lack hardware support for some newer formats, such as VP9, AV1, and 10 bit HEVC, so a shorter list is not necessarily an error.

AMD (from the documentation, not tested)

AMD needs no separate driver, because AMD uses the VA-API support built into Mesa. Fedora's Mesa is built without hardware acceleration for H.264, H.265, and VC-1 for licensing reasons. RPM Fusion's freeworld builds add it back. The current RPM Fusion guide gives:

sudo dnf install mesa-va-drivers-freeworld
sudo dnf swap mesa-vulkan-drivers mesa-vulkan-drivers-freeworld
sudo dnf install libva-utils
vainfo

The output typically mentions Mesa Gallium driver and AMD Radeon. Only add the matching .i686 packages if you use 32 bit programs such as Steam:

sudo dnf install mesa-va-drivers-freeworld.i686
sudo dnf swap mesa-vulkan-drivers.i686 mesa-vulkan-drivers-freeworld.i686

Earlier guides also swapped the VDPAU driver for a freeworld build. RPM Fusion's current guide does not mention that, so I have left it out.

NVIDIA (from the documentation, not tested)

With NVIDIA's proprietary driver from RPM Fusion, VDPAU, NVENC, and NVDEC are ready to use. The driver has no native VA-API support, so RPM Fusion offers a wrapper that translates VA-API to NVDEC:

sudo dnf install akmod-nvidia
sudo dnf install libva-nvidia-driver

The current driver family has dropped support for GPUs older than Pascal. Older cards need a legacy driver family, for example 580xx for Maxwell and Pascal or 470xx for Kepler. Follow RPM Fusion's NVIDIA guide to pick the right one.

Common to all three

  • Only install the driver that matches your chip, and do not mix them.
  • Browsers do not necessarily use VA-API automatically. That is a separate setting in each browser, so check your browser's own documentation.
  • I tested the Intel commands myself. The AMD and NVIDIA commands come from RPM Fusion's documentation and are not tested by me.

โฐ 6. Automatic updates with dnf5 automatic

Updates only protect you once they are installed. dnf5-plugin-automatic is part of dnf5 and installs updates on a schedule. Its default settings live in /usr/share/dnf5/dnf5-plugins/automatic.conf. Do not edit that file, because a package update can overwrite it. Put only your own overrides in /etc/dnf/automatic.conf, which takes precedence:

[commands]
upgrade_type = default
random_sleep = 0
network_online_timeout = 60
download_updates = yes
apply_updates = yes
reboot = never

[emitters]
emit_via = stdio
emit_no_updates = no

Use only one section of each kind. I once had an extra [commands] block in the file, which gave duplicate settings, and then it is unclear which value actually applies. You can see the effective lines, without comments and blank lines, like this:

sudo grep -vE '^\s*(#|$)' /etc/dnf/automatic.conf

Enable the timer:

sudo systemctl enable --now dnf5-automatic.timer

Check that it works:

systemctl status dnf5-automatic.timer
journalctl -u dnf5-automatic.service
sudo dnf history list

A few things to know:

  • apply_updates = no only downloads the updates. You then install them yourself.
  • With reboot = never I reboot manually. sudo dnf needs-restarting tells you whether a reboot is recommended. In dnf5 the old -r option is only kept for compatibility, because that is now the default behaviour.
  • An update of Docker can restart your containers, so keep that in mind if you run services on the machine.

๐Ÿ›ก๏ธ 7. Check the security basics

A few quick checks tell you whether the foundation is in place.

sestatus

SELinux should be enforcing. If SELinux blocks something, find out why instead of running audit2allow by reflex, because that can permanently allow exactly what SELinux was meant to stop.

sudo firewall-cmd --list-all

Look through the list of services and remove the ones you do not use:

sudo firewall-cmd --permanent --remove-service=SERVICE
sudo firewall-cmd --reload
fwupdmgr security

shows the platform security of the firmware, such as whether protection features are enabled.

lsblk -f

shows whether the disk is encrypted: an encrypted partition shows up as crypto_LUKS. Encryption is chosen during installation. It cannot be added afterwards without risk, so if the disk is not encrypted, plan it for the next install.

mokutil --sb-state

shows whether Secure Boot is enabled. Finally, Lynis gives a broader audit with concrete suggestions:

sudo dnf install lynis
sudo lynis audit system

๐Ÿงน 8. Clean up third party repositories

Every extra repository is software you trust with root access, and one more thing that can block an upgrade. Keep only the ones you actually use:

dnf repo list

Before upgrading to a new Fedora version, test whether each third party repository is ready for it. Ask for its repodata/repomd.xml file for the new version number:

curl -sL -o /dev/null -w '%{http_code}' https://example.com/fedora/46/x86_64/repodata/repomd.xml

200 means it is ready, 404 means it is not. If one is missing, leave it out during the upgrade with --disablerepo=REPO_ID and turn it back on when it catches up.

๐Ÿ” 9. Permissions

Sensible permissions mean that other users and programs cannot read what they should not:

  • The home folder: 700
  • Folders: 755
  • Files: 644
  • Private files, such as keys: 600
  • Avoid 777, which lets everyone write everywhere.
chmod 700 ~
chmod 600 ~/.ssh/id_ed25519

If a program cannot access a file, fix the owner with chown instead of opening it up for everyone:

sudo chown USER:USER FILE

๐Ÿ”ค 10. Fonts and cleanup

Fedora has good fonts, but if you read or write other scripts, install the matching packages. For example:

sudo dnf install google-noto-sans-fonts google-noto-sans-tamil-fonts google-noto-sans-malayalam-fonts

Finally, remove what is no longer needed:

flatpak uninstall --unused
sudo dnf autoremove

Read the list before you confirm, so nothing you use disappears.

โœจ 11. New in Fedora 45

These points come from Fedora's change pages for Fedora 45, and I have not tested them separately:

  • Signed packages are required by default. rpm now only installs packages with a verified signature, unless you override it with --nosignature. Unsigned local RPM files that used to install fine can therefore be refused, for example when you reinstall them.
  • ptrace is restricted by default. The kernel limits debugging operations for ordinary users. Installing a debugger such as gdb pulls in the package that lifts the restriction again.
  • Repository configuration has moved from /etc to /usr. The configuration that Fedora itself ships now lives in /usr/share/dnf5/repos.d instead of /etc/yum.repos.d. Your own changes in /etc still take precedence.

โœ… Conclusion

After these steps the system is up to date, plays the common video formats with hardware acceleration, installs updates by itself, and has a checked security baseline. Most of it takes less than half an hour.

๐Ÿš€ Next steps

  • Backup: set up a backup before you need it, and test that you can actually restore from it.
  • Disk encryption: if the disk is not encrypted, choose encryption at your next install.

Sources