Guides 11792 Published by

The guide explains how to get the feature‑rich Vivaldi browser onto an AlmaLinux 9 system, starting with a quick update check and internet verification before adding the official RPM repository. It walks through importing the GPG key, installing the package via dnf, and launching the browser, while noting that the process skips manual confirmation for speed yet can be left to user discretion. The author also covers common hiccups such as missing libXss or GPG verification failures, offering straightforward fixes like reinstalling dependencies or refreshing the repo file. For users who prefer Snap, a brief section shows how to set up snapd and install Vivaldi with classic confinement, concluding with an invitation to reach out for help if any unforeseen issues arise.



How to Install Vivaldi Browser on AlmaLinux 9

If you’re tired of Chromium’s endless updates and want a slick, feature‑packed browser that still feels like a desktop app, Vivaldi is worth the effort. Below are the steps I use every time I add it to an AlmaLinux 9 machine – no magic required.

Why Vivaldi Works on AlmaLinux 9

Vivaldi ships as a standard RPM that’s compatible with any RHEL‑based distro. Unlike some bleeding‑edge browsers, its dependencies are deliberately minimal, so you won’t hit “cannot install because of conflicting packages” after a quick sanity check.

Prerequisites and Quick Checks
  • Make sure your system is fully updated:

sudo dnf update -y – it catches those stray kernel modules that can trip up the GPG verification step later.

  • Verify you have a working internet connection; Vivaldi’s repo URL will be fetched from the network.

If you’re on a minimal install, the only missing package is `dnf`, which should already be there on AlmaLinux 9.

Step‑by‑Step Installation

1. Add the official Vivaldi repository

   sudo dnf config-manager --add-repo=https://repo.vivaldi.com/archive/rpm/vivaldi.repo

This tells DNF where to look for the package and keeps it in sync with new releases.

2. Import the GPG key – this guarantees the binary hasn’t been tampered with.

   sudo rpm --import https://repo.vivaldi.com/archive/rpm/RPM-GPG-KEY-VIVALDI

Without this, DNF will complain about an unsigned package.

3. Install Vivaldi

   sudo dnf install vivaldi -y

The `-y` flag skips the confirmation prompt; I do it for speed on fresh installs but feel free to check the list manually if you’re cautious.

4. Launch it – either via the application launcher or by running `vivaldi` in a terminal. Your first run will download a few additional components (fonts, plugins) over the network.

Troubleshooting Common Issues
  • Missing dependencies?

If DNF stops at “Error: No matching package…”, you’re probably missing `libXss`. Install it with `sudo dnf install libXScrnSaver` and try again. I’ve seen this happen after a recent kernel upgrade that left the libX packages out of sync.

  • GPG verification fails

Delete the repo file (`/etc/yum.repos.d/vivaldi.repo`) and re‑add it. A stale key can cause the signature check to fail; reimporting fixes most cases.

  • Snap or Flatpak conflict?

If you already have a Snap version of Vivaldi, uninstall it first: `sudo snap remove vivaldi`. Mixing package managers on the same app is a recipe for broken binaries.

Optional: Adding the Snap Package

If you prefer to stay on Snap for automatic updates, install Snapd (`sudo dnf install snapd`) and then:

sudo ln -s /var/lib/snapd/snap /snap
sudo snap install vivaldi --classic

It’s a bit slower to start up than the RPM version, but if you’re already using many Snaps, it keeps your system tidy.

That’s all there is to it. Vivaldi should now be running like any other app on your desktop. If you hit a snag that isn’t covered here, drop me a line – I’ve seen everything from “cannot locate libXv” to “profile corrupted after a crash” and can usually point you in the right direction.