If you want a Fedora Synaptic alternative that shows RPM packages, Flatpaks, updates, and queued changes in one GTK application, Yum Extender NG gives you a graphical front end for the DNF5 stack. Its current upstream project targets Fedora 42 through 44 and Rawhide through the stable COPR repository.
Yum Extender is not a replacement for understanding package sources. It makes selection and review easier, while DNF and the enabled repositories still decide what your system can install.
What Yum Extender NG manages on Fedora
Yum Extender NG, also called yumex, is a graphical package tool for RPM packages and Flatpaks. The current upstream README says that its latest generation uses GTK4, libadwaita, the DNF5 daemon, and libflatpak for package actions.
That makes it useful when you want to search packages, inspect versions and descriptions, stage several changes, then review them before applying them. Use the terminal when you need a command in an automated workflow or want to inspect DNF output directly.
Choose a package from the list or search control, inspect its summary and version, then add the intended action to the queue. Review the queue before selecting Apply so you can catch an unwanted removal or dependency change.
Install Yum Extender from its stable COPR repository
The yumex package comes from the maintainer’s COPR repository rather than Fedora’s main repositories, so enable it only when you trust the owner and can account for it during future package-conflict diagnosis.
sudo dnf copr enable timlau/yumex-ng
sudo dnf install yumex
The project’s stable COPR page publishes the same repository name and package command, lists Fedora 43 and Fedora 44, and the upstream repository also names Fedora 42 through 44 and Rawhide for its COPR packages.
Read the COPR warning before confirming. The repository owner, not the Fedora project, controls its packages and update cadence.
After installation, open Yum Extender from the application launcher or run yumex from a terminal, then confirm the COPR repository is enabled and supports your Fedora release if DNF cannot find the package.
Use the package list without losing track of changes
Start in Packages to browse RPM packages by name, version, architecture, size, and summary, then use those details to separate a runtime package from a development or documentation package.
Use Installed when you need to review what is already present, Updates when you are preparing maintenance, and Search when you know part of a package name. The Flatpaks tab is separate, so confirm which packaging system you are changing before you queue an action.
Yum Extender collects your selections in Queue instead of applying every click immediately. Open that tab before Apply and check the full transaction, especially when an update pulls in a replacement package or removes a dependency.
Manage repositories carefully
The Repository view exposes enabled sources, but it does not make every source appropriate for every system. Keep the Fedora repositories enabled unless you have a specific reason to change them, and disable a third-party repository when you no longer need its packages.
If you later remove Yum Extender, disable the COPR repository first when you do not want packages from it offered during updates. For a command-line view of enabled sources and their priorities, see how to enable or disable Fedora repositories.
When Yum Extender is the wrong choice
Use Yum Extender on a current Fedora system with DNF5 support. The upstream project states that it follows recent GTK4, libadwaita, and DNF5 development closely, so it is not a good fit for long-lived enterprise releases such as Red Hat Enterprise Linux.
Immutable Fedora variants use a different operating-system update model. If you are choosing a Fedora-derived gaming system, read the Bazzite review and installation notes before assuming a DNF desktop workflow applies unchanged.
Keep the graphical view connected to Fedora maintenance
Yum Extender helps you see a transaction before it runs, but it does not remove the need for basic package-management habits. Learn how dependencies, package sources, updates, and removals fit together in this Linux package-management overview.
For a new Fedora installation, pair your package choices with the steps in what to do after installing Fedora. When system maintenance leaves older kernels behind, use the Fedora-specific steps in how to remove old Fedora kernels rather than deleting kernel packages blindly.
Is Yum Extender a Synaptic replacement for Fedora?
Yum Extender gives Fedora a graphical way to search, queue, install, remove, and update RPM packages, plus a separate Flatpaks view. It is a comparable package-management interface, but it uses Fedora’s DNF5-based package stack rather than APT.
How do I install Yum Extender on Fedora?
Enable the stable timlau/yumex-ng COPR repository with sudo dnf copr enable timlau/yumex-ng, then install the yumex package with sudo dnf install yumex. Confirm that the COPR repository supports your Fedora release before proceeding.
Does Yum Extender work on Red Hat Enterprise Linux?
The Yum Extender upstream project says its current release follows recent GTK4, libadwaita, and DNF5 development closely, so it is not a suitable choice for long-lived releases such as Red Hat Enterprise Linux.
Install only the packages and sources you can explain, then review the queue before applying changes. That one pause is where a graphical package manager earns its place.