Fedora 45 reached general availability in early November 2026, so this is the first week many people are rebuilding laptops and workstations on it. Vivaldi is not in Fedora’s default repositories, so the browser needs a few deliberate steps. Fedora 45 ships with DNF5 and RPM 6.1, which adds stricter package signature checking. That makes old copy-and-paste tutorials risky, and some of them fail outright.

The usual symptom is a command like dnf config-manager --add-repo that errors out on a fresh system. DNF5 replaced that flag, and a lot of blog posts never caught up. A LinuxCapable maintainer noted in a reply to a reader that the old --add-repo flag no longer works in DNF5 and updated their guide to match. Other posts tell people to download a loose RPM and double-click it. That works once, but you then have a browser that never updates, and an unpatched Chromium-based browser is a real security liability.

This guide takes the approach a sysadmin would use on a machine they have to maintain for years. It adds the vendor repository, imports the signing key, installs the stable channel, and lets DNF handle updates. It also covers the manual RPM route, the snapshot channel, Wayland behavior, codecs, hardening, troubleshooting and clean removal. The commands target Fedora 45 Workstation, and most of the logic carries over to Fedora 44, Nobara and other RPM-based systems with small changes.

Why the Repository Method Wins

Fedora does not ship Vivaldi in its default repositories, but Vivaldi publishes an RPM repository. With it, DNF handles installation, updates and removal for both vivaldi-stable and vivaldi-snapshot. Chromium-based browsers get security patches often, and sometimes within days of a zero-day disclosure. A one-off RPM download gives you none of that unless you remember to repeat it.

There is a second reason, and it shows up on fleets. A repository can be mirrored, pinned, audited and scripted. If you manage ten developer laptops, one .repo file in your configuration management tool beats ten people visiting a download page.

Vivaldi’s own help documentation also covers the direct-install route. For Fedora-based distributions it uses sudo dnf --nogpgcheck -y install ./vivaldi*.rpm on a downloaded package. Treat --nogpgcheck with suspicion. It disables signature verification, which is the opposite of what you want, and it is unnecessary once the key is imported properly. The steps below avoid it.

Before You Start: Prerequisites

Check three things first. They take a minute and prevent most of the errors covered in the troubleshooting section.

• Architecture. Vivaldi’s repository path uses $basearch, so x86_64 works out of the box. Confirm with uname -m. ARM64 packages exist on Vivaldi’s side, but check availability for your hardware before relying on them.
• Network access. Your machine needs HTTPS access to repo.vivaldi.com. Corporate proxies sometimes block it.
• Privileges. You need a user in the wheel group with sudo.

Then refresh the system so DNF works with current metadata:

sudo dnf upgrade --refresh

If the upgrade pulls in a new kernel, reboot before continuing. Installing a browser on a half-updated system is how people end up chasing dependency mismatches that disappear after a reboot.

Step 1: Add the Official Vivaldi Repository

On Fedora 45, DNF5 can pull a vendor repo file straight from a URL. This is the command:

sudo dnf config-manager addrepo --from-repofile=https://repo.vivaldi.com/stable/vivaldi-fedora.repo

If DNF reports that config-manager is missing, the plugin package isn’t installed on your trimmed-down system. Install it and run the command again:

sudo dnf install dnf5-plugins

The command writes a short file into /etc/yum.repos.d/. Look at what it contains before you trust it:

cat /etc/yum.repos.d/vivaldi-fedora.repo

The file defines a repository named vivaldi that is enabled, points at https://repo.vivaldi.com/archive/rpm/$basearch, has gpgcheck=1, and references the signing key at https://repo.vivaldi.com/archive/linux_signing_key.pub. Reading it takes ten seconds and is a good habit with any third-party repo. You want to see HTTPS, signature checking on and no surprises.

Verify that DNF sees the repository:

dnf repo list --enabled | grep -i vivaldi

One oddity confuses people. The word archive appears in the baseurl and in later key-import messages. That is expected, because the repo file points Fedora at Vivaldi’s /archive/ RPM path. It does not mean you are on an old or abandoned mirror.

Step 2: Install Vivaldi Stable

Now the install itself:

sudo dnf install vivaldi-stable

DNF will resolve dependencies and ask you to confirm. On the first install from this repository it also asks whether to import the Vivaldi signing key. Compare the fingerprint it shows against the one published on Vivaldi’s site if you want to be rigorous, then accept. DNF imports the key the first time you install a package from the repository.

On a normal Workstation install the transaction is small, since most libraries are already present. On a minimal or cloud image the same command can pull in a large part of the desktop stack, such as GTK, fonts and audio libraries. That is not a bug. It is the dependency tree doing its job.

Confirm the result:

rpm -q vivaldi-stable
vivaldi-stable --version

Launch it from the application grid, or from a terminal with vivaldi. On first run, the setup wizard asks about theme, tab position and privacy defaults. Pick what you like. Everything can be changed later.

A note on the second repo file

After installation, you may notice two files in /etc/yum.repos.d/: vivaldi.repo and vivaldi-fedora.repo. The first is created by the package’s post-install script, and the second by config-manager addrepo. They share the repository ID vivaldi, and DNF treats them as one repo. It is harmless. If you want things tidy on a server-style setup, keep one and document which.

Step 3: Choose Your Channel

Vivaldi publishes more than one build, and which you pick depends on how much instability you will tolerate.

The snapshot package installs alongside stable and uses its own configuration directory, so you can run both on one system. That is useful for web developers who want to check how a site behaves in the newest engine without risking their main profile.

sudo dnf install vivaldi-snapshot

Practical advice: keep stable as your primary browser, and run snapshot only for testing. Never sync a profile you care about into an experimental build without a backup.

Alternative: Install a Downloaded RPM

Sometimes the repository is off the table. You may be on an air-gapped network, behind a proxy that allows only specific downloads, or building a golden image. In that case you can install the RPM directly.

Download the package from Vivaldi’s download page, then from the folder where it landed:

sudo dnf install ./vivaldi-stable*.rpm

Use dnf rather than rpm -i. DNF resolves dependencies automatically, while raw rpm just fails and lists what is missing. Vivaldi’s own help page documents the same approach with a local file path.

Here is the part many guides skip. The package’s post-install script normally drops a repo file in place, which is how later updates arrive. So even the “manual” install usually ends up on the repository path. Check with dnf repo list | grep -i vivaldi after installing. If nothing shows up, you are stuck on a static version and must either re-add the repo or update by hand.

You can also install straight from a URL, but resolving the latest filename programmatically is fragile. A repository listing scrape works, though it breaks whenever the page layout changes. For anything repeatable, prefer the repo.

Verifying Integrity and Trust

A browser is the most exposed application on a desktop, so verification matters more than usual. Here are a few checks worth doing.

Check where a package came from:

dnf info vivaldi-stable

The “From repository” line should say vivaldi. Then verify the installed files against the RPM database:

rpm -V vivaldi-stable

No output means nothing has been modified. Output with flags such as S or 5 on a file means size or checksum changed, which warrants a look.

Fedora 45 helps here. The release brings RPM 6.1 with enhanced package signature checking, and it blocks a package vendor from silently changing. In practice, if a third-party repo ever switches its signing identity, you should see a clear prompt instead of a quiet swap. That is the behavior you want from a package manager, so read those prompts rather than reflexively pressing “y”.

If you ever need to import the key manually, for example in a kickstart or automation context, use:

sudo rpm --import https://repo.vivaldi.com/archive/linux_signing_key.pub

That key URL matches the one referenced in the repo file.

Keeping Vivaldi Updated

Once the repo is enabled, Vivaldi updates alongside everything else:

sudo dnf upgrade --refresh

To update only the browser:

sudo dnf upgrade vivaldi-stable

To see what’s pending without installing anything:

dnf check-upgrade

On personal machines, GNOME Software or Discover will also surface updates, though DNF talks directly to the repository without an extra layer, which makes it easier to debug when something goes wrong. For unattended updates, Fedora offers dnf5-plugin-automatic. A cautious setup is to apply security updates automatically and leave the rest for a manual window:

sudo dnf install dnf5-plugin-automatic
sudo systemctl enable --now dnf5-automatic.timer

Check /etc/dnf/automatic.conf for the apply-updates setting and your preferred notification method. One caveat: a running browser keeps using old binaries until restarted. After an automatic update, Vivaldi may show a prompt to relaunch. Do it. Leaving a browser open for three weeks after a security fix defeats the purpose.

Wayland, Display and Hardware Acceleration

Fedora Workstation uses Wayland by default, and Chromium-based browsers have improved a lot there. Still, behavior varies by GPU, driver and desktop environment, and this is where most “weird” reports come from.

Vivaldi is Chromium-based, so it accepts Chromium-style flags. The Ozone platform hint controls whether it runs natively on Wayland or through XWayland:

vivaldi --ozone-platform-hint=auto

If text looks blurry on a HiDPI display, native Wayland usually fixes it. If you see flickering, black windows or a broken cursor, try forcing X11:

vivaldi --ozone-platform=x11

Test from the terminal first. Once something works, make it permanent by copying the desktop file to your user directory and editing the Exec= line:

mkdir -p ~/.local/share/applications
cp /usr/share/applications/vivaldi-stable.desktop ~/.local/share/applications/

Edit the copy rather than the system file. Package updates overwrite files under /usr/share, and your tweak vanishes without warning. Flags can also be checked on the internal page vivaldi://gpu, which shows whether video decode, rasterization and WebGL are hardware-accelerated.

Hardware video decode on Fedora depends on your GPU stack. Intel and AMD usually go through VA-API. NVIDIA is more complicated and depends on driver and packaging choices. If vivaldi://gpu shows software decoding and your fans spin up on 4K video, that is your clue.

Media Codecs and Streaming

Fedora’s default repositories avoid some patent-encumbered codecs. Vivaldi bundles its own media support through its package, so many sites work out of the box. But if a specific site refuses to play video, or you have trouble with hardware decoding, you may need extra multimedia packages from RPM Fusion.

Enable RPM Fusion following the project’s current instructions, then swap or install the relevant multimedia packages. Check RPM Fusion’s own documentation first, since the exact commands change between Fedora releases. Do this only if you have a concrete problem. Adding more third-party repos widens your attack surface and creates update conflicts, so a clean system is easier to maintain.

DRM-protected streaming is a separate topic that depends on the Widevine component. If a service reports a DRM error, check vivaldi://components and try updating the Widevine entry.

Performance Tuning

A browser can be a real resource hog. A few settings help on modest hardware, and here is what matters in practice.

• RAM. Open vivaldi://memory-internals or the built-in task manager (Shift+Esc) to find the tab or extension eating memory. Vivaldi’s tab hibernation feature frees memory from background tabs and is worth enabling on 8 GB machines.
• CPU. Heavy extensions and background sync loops show up here. Disable what you do not use.
• Disk I/O. Profiles live under ~/.config/vivaldi/. On a spinning disk or a slow SD card, a large profile with many extensions makes startup sluggish. Keep the profile on SSD storage.
• Network. If DNS is slow, consider enabling secure DNS in the browser settings, or run a local caching resolver such as systemd-resolved with a good upstream.

On shared machines or terminal servers where several people run browsers at once, resource limits matter. A systemd user slice can cap memory so one runaway tab doesn’t freeze the session:

systemd-run --user --scope -p MemoryMax=4G -p MemoryHigh=3G vivaldi

That runs Vivaldi in its own cgroup scope with a soft limit at 3 GB and a hard limit at 4 GB. It is crude, but it saves sessions during traffic-heavy testing, such as load-testing a web app by opening dozens of tabs.

Troubleshooting Common Problems

“Unknown argument –add-repo”

This is the classic Fedora 45 failure. DNF5 dropped the old flag. Use the newer syntax: sudo dnf config-manager addrepo --from-repofile=URL. Commands written for DNF4 that use --add-repo fail on current Fedora, as readers of older guides have reported.

“No match for argument: vivaldi-stable”

The repo is missing or disabled. Run dnf repo list --all | grep -i vivaldi. If it shows as disabled, enable it with sudo dnf config-manager setopt vivaldi.enabled=1. If it is absent, repeat Step 1. Also check that you are on x86_64, since the baseurl depends on architecture.

GPG key errors or signature failures

First, refresh and retry: sudo dnf clean all && sudo dnf makecache. If the key is still rejected, import it manually with the rpm --import command shown earlier. Fedora 45’s RPM 6.1 enforces signature checks more strictly, so a stale or missing key is more likely to surface as a hard error than before. Do not “fix” this with --nogpgcheck unless you understand the risk and have verified the package by other means.

Metadata download failures or timeouts

Check connectivity with curl -I https://repo.vivaldi.com/archive/rpm/x86_64/. If it hangs, suspect a proxy, a DNS problem or a captive portal. Setting proxy= in /etc/dnf/dnf.conf helps in corporate networks.

Vivaldi won’t start or crashes immediately

Launch it from a terminal and read the output. Common causes include a corrupted profile, a GPU driver problem or a conflicting flag. Try a fresh profile directory:

vivaldi --user-data-dir=/tmp/vivaldi-test

If that works, your main profile is the problem. Back it up and then try disabling extensions. If it fails too, try --disable-gpu to rule out graphics trouble.

Blurry fonts or wrong scaling on Wayland

Use the Ozone flag described earlier. Fractional scaling interacts with the browser’s own zoom, so check both.

Video plays without sound, or not at all

Check PipeWire with wpctl status. Confirm the right output device is selected. If a specific site fails, revisit the codec and Widevine notes above.

Duplicate repository warnings

Seeing both vivaldi.repo and vivaldi-fedora.repo is normal, since they share the same ID. If warnings bother you, keep one.