Story / scenario opener
You just finished a clean Fedora Workstation install and the GNOME interface feels too heavy for your daily workflow. You want a cleaner, more traditional desktop that gets out of your way and lets you focus on terminal work or development. You decide to try Budgie. You open the terminal, type sudo dnf install budgie-desktop, and watch the package manager refuse the request with a missing repository error.
What is actually happening
Fedora ships with GNOME as the default desktop environment. The core packaging team maintains strict guidelines that exclude proprietary codecs, firmware blobs, and third-party desktop environments from the official repositories. Budgie lives outside those official channels. It is maintained by the Solus project and packaged for Fedora by community contributors. To install it, you need to point dnf at a third-party repository that hosts the packages and their dependencies.
RPM Fusion fills that gap. It splits packages into free and nonfree tiers. The free tier contains open-source software that complies with Fedora's packaging standards. The nonfree tier holds firmware, proprietary codecs, and hardware drivers that Fedora cannot distribute directly due to licensing restrictions. Adding RPM Fusion does not break your system. It simply expands the package index dnf consults during transactions. The package manager will still prefer official Fedora packages when both sources provide the same software. Third-party packages only install when they are the sole source or when explicitly requested.
Desktop environments in Fedora are distributed as package groups. A group is a metadata collection that bundles related packages under a single identifier. When you install a group, dnf resolves the entire dependency tree, pulls the core components, recommended extensions, and default configuration files in one atomic transaction. This prevents partial installations that leave the desktop environment broken or missing critical libraries.
Run dnf group list hidden to see all available desktop environments before committing to one. The output shows which groups are already installed and which are available. This prevents accidental duplication and helps you plan disk space allocation.
How to install Budgie
You need to enable the RPM Fusion repositories first. Run the setup command that pulls the release packages for your exact Fedora version. The command uses an RPM macro to auto-detect the release number. This prevents you from accidentally installing packages built for an older or newer Fedora release.
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 -y
# -y automatically answers yes to the GPG key import prompt
# The rpm macro expands to your current release number at runtime
# This step registers the repository metadata in /etc/yum.repos.d/
After the repositories are registered, refresh the package cache. dnf caches metadata to speed up lookups and reduce bandwidth usage. A fresh install of a third-party repo requires a manual refresh so the package manager sees the new package lists immediately.
sudo dnf upgrade --refresh
# --refresh forces dnf to download fresh metadata from all enabled repos
# This is the standard weekly maintenance command on Fedora
# It ensures dependency resolution uses the latest available versions
Now install the desktop environment group. Fedora groups related packages under a single identifier. The groupinstall command pulls the core Budgie packages, recommended extensions, and default configuration files in one transaction.
sudo dnf groupinstall "Budgie Desktop"
# groupinstall resolves the entire desktop stack at once
# It pulls in the window manager, panel applets, and theme assets
# The quotes prevent shell globbing from breaking the package name
The transaction will download several hundred megabytes depending on your current system state. Fedora Workstation already includes many shared GTK libraries and system utilities. The package manager will skip those and only fetch Budgie-specific components. Watch the dependency resolution phase. If dnf reports a conflict, stop the transaction. Do not force the install. Read the conflict message and verify you are using the group identifier rather than a single package name.
Verify it worked
Log out of your current session. Do not reboot. The display manager handles session switching without a full system restart. At the login screen, look for a gear icon or a session menu near the password field. Click it and select Budgie. Enter your password and press enter. The display manager loads the Budgie session profile and starts the panel, window manager, and background services. If the desktop loads with a clean top bar and a left-aligned dock, the installation succeeded.
Check the running session type with the following command. This confirms whether Budgie launched under Wayland or fell back to X11.
echo $XDG_SESSION_TYPE
# Returns wayland or x11 depending on your hardware and driver stack
# Wayland is the default on modern Fedora systems with supported GPUs
# X11 fallback occurs when proprietary drivers or remote desktop tools are active
Verify that the panel applets are loading correctly by checking the system journal for Budgie-specific messages. Filter the output to avoid drowning in unrelated service logs.
journalctl -xeu budgie-panel.service --no-pager -n 10
# -x adds explanatory text to journal entries
# -e jumps to the end of the log buffer
# -u scopes the output to the Budgie panel service
# --no-pager and -n 10 keep the output short and readable
If the output shows Started Budgie Panel with no red error lines, the desktop environment is running normally. Close the terminal and test window snapping, workspace switching, and the application menu. Budgie uses a modified GNOME Shell backend for window management. Expect familiar keyboard shortcuts like Super+Arrow for snapping and Super+Tab for application switching.
Common pitfalls and what the error looks like
The most common failure happens when the RPM Fusion GPG keys are not imported correctly. The transaction will abort with Error: GPG check FAILED. Run sudo rpm --import /etc/pki/rpm-gpg/RPM-GPG-KEY-rpmfusion-free-fedora-$(rpm -E %fedora) to fix it. Always verify the key fingerprint matches the official RPM Fusion documentation before importing.
Another frequent issue involves conflicting desktop environments. Fedora Workstation installs GNOME by default. Installing a second desktop environment does not remove GNOME. Both will coexist. If you see Transaction test error: package gnome-shell conflicts with budgie-desktop, you are likely trying to force a replacement that breaks the base system. Do not use --skip-broken or --force here. The conflict usually means you ran dnf install budgie-desktop instead of dnf groupinstall "Budgie Desktop". The group package handles the dependency tree correctly and avoids pulling conflicting window manager components.
Display manager configuration is another tripwire. Fedora uses GDM3. GDM3 reads session files from /usr/share/wayland-sessions/ and /usr/share/xsessions/. The Budgie package drops a .desktop file into those directories automatically. If the session option does not appear in the login menu, run ls /usr/share/wayland-sessions/budgie.desktop to verify the file exists. If it is missing, reinstall the group package. Never edit session files in /usr/lib/ or /usr/share/. Those paths are owned by the package manager. User modifications belong in /etc/ or ~/.config/. Package updates will overwrite manual edits in system directories.
Theme conflicts occasionally break the visual layout. Budgie ships with a default dark and light theme. If you previously installed global GTK themes or icon packs, they may override Budgie's defaults and cause missing icons or broken panel elements. Reset the theme to the distribution default by running gsettings reset org.gnome.desktop.interface gtk-theme. The display manager will apply the clean theme on the next login.
Run journalctl -xe first. Read the actual error before guessing.
When to use this versus alternatives
Use Budgie when you want a traditional desktop layout with modern GTK4 applications and minimal configuration overhead. Use GNOME when you rely on heavy tiling extensions, dynamic workspaces, and the default Fedora experience. Use KDE Plasma when you need granular control over every window behavior, system tray icon, and compositor setting. Use XFCE when you are running older hardware and need the lowest possible memory footprint. Stay on the default GNOME if you only deviate from the defaults occasionally and prefer a stable, unmodified base.