How To Install GIMP on Fedora 45

Install GIMP on Fedora 45

Few things are more annoying than a fresh Fedora install where the image editor you need for tomorrow’s deadline is missing or behaves oddly. Fedora 45 is out, with GNOME 51, KDE Plasma 6.8 and kernel 7.2. It is a clean base for creative work, but it ships with no image editor by default. You still have to choose how GIMP gets onto the machine.

That choice matters more than most tutorials admit. Fedora has three realistic paths: the native RPM through DNF, the Flatpak build from Flathub, and the Snap package. Each one changes how updates arrive, how plugins behave, how much disk space you burn, and how the application is sandboxed. A designer on a laptop and an admin building a shared workstation image have different needs.

This guide covers the install itself, then the parts that usually go wrong. That means missing plugins, Wayland tablet quirks, sandbox permissions, slow canvas performance and broken menu entries. The commands are for Fedora 45, but most of the logic carries over to Fedora 44 and 43, and the dnf and Flatpak sections also apply on AlmaLinux or Ubuntu with small changes.

What You Get on Fedora 45

Fedora 45 carries the GIMP 3.2 series in its repositories. The package announce list shows gimp-3.2.6-1.fc45 as an update for Fedora 45. The upstream project lists 3.2.8 as the current stable release, dated 2026-11-02. So the repository build can sit a patch release or two behind upstream, which is normal for a distribution that tests updates before shipping them.

That gap rarely matters. If a bug fix landed in 3.2.8 that you need today, Flatpak is usually the quicker route. If you value a conservative system that updates alongside everything else, the RPM is the better fit.

GIMP 3 is a major break from the 2.10 line. The interface moved to GTK3, Wayland support is much better, and the plugin API changed. Fedora’s own change proposal warned that third-party GIMP 2 plugins may not work with version 3. If you carry old Script-Fu or Python plugins from a previous machine, expect to retest them.

Choosing an Install Method

Method Source Updates Sandboxed Best for
DNF (RPM) Fedora repositories With dnf upgrade No Daily desktops, system integration
Flatpak Flathub With flatpak update Yes Newest upstream release, isolation
Snap Snap Store Automatic via snapd Yes Rare; only if you already use snaps

Anyone planning to install GIMP on Fedora 45 should settle on one method and stay with it. Running the RPM and the Flatpak side by side works technically. In practice it creates two sets of preferences, two sets of plugins and a lot of confusion about which one opened that file.

A rough rule from practical use: pick DNF unless there is a reason not to. The RPM links against system libraries, picks up system fonts without extra setup, and can reach the whole filesystem. Pick Flatpak when you want the latest release, or when the machine is shared and you want the app contained.

Before You Install: Prepare the System

Start by refreshing metadata and applying pending updates. Installing onto a stale system is the classic way to hit dependency conflicts.

sudo dnf upgrade --refresh

If the kernel or core libraries were updated, reboot before continuing. It sounds cautious, but half-updated graphics stacks cause odd GIMP rendering problems that look like application bugs.

Check free disk space next. The RPM and its dependencies are modest. The Flatpak is heavier because it brings its own runtime. One third-party guide estimates 400 to 600 MB for the Flatpak install including the runtime. Check your free space.

df -h / /var /home

Flatpak system installs live under /var/lib/flatpak, and user installs live under ~/.local/share/flatpak. If /var is a small separate partition on a server image, that detail will bite you.

Method 1: Install GIMP with DNF

This is the shortest route. Look at what Fedora offers before you commit.

dnf info gimp

You should see a 3.2.x version tagged fc45. Then install:

sudo dnf install gimp

DNF will list the dependencies, including gimp-libs and GEGL-related libraries, and ask for confirmation. Accept it. A third-party Fedora 44 guide uses the same plain sudo dnf install gimp command, and the same approach carries over to Fedora 45.

Confirm what landed on disk:

rpm -q gimp
gimp --version

The output should show a gimp-3.2.x-...fc45 package and a matching “GNU Image Manipulation Program version 3.2.x” line. Any 3.x version confirms the correct generation is installed.

Launch it from the application menu, or from a terminal:

gimp

Starting from a terminal is worth doing the first time. If a plugin or library complains, the message shows up there rather than disappearing silently.

Why the package name is just “gimp”

Older Fedora releases used gimp3 as a separate package during the transition. Fedora folded GIMP 3 into the main gimp package starting with Fedora 41, and the gimp3 name was retired for newer releases. Fedora Packages still lists gimp3 only under older releases such as Fedora 40. On Fedora 45, ignore gimp3 and use gimp.

Optional extras from the repositories

Search for add-ons rather than guessing names:

dnf search gimp
dnf search gegl

You will see items such as help files, language packs and developer tools. The gimp-devel-tools package, for example, provides plugin and extension development tools and also exists for Fedora 45. Most users never need it. Developers writing plugins will.

If you work with camera RAW files, GIMP normally hands them off to a RAW processor such as darktable or RawTherapee. Install one of them from the same repositories:

sudo dnf install darktable rawtherapee

Without one, opening a .CR3 or .ARW file produces an error or a dialog asking for a plugin.

Method 2: Install GIMP with Flatpak

Fedora Workstation, Silverblue and Kinoite normally include Flatpak already, while minimal or server installs may not. Check first:

flatpak --version

If the command is not found:

sudo dnf install flatpak

Add the Flathub remote. The --if-not-exists flag makes the command safe to repeat:

sudo flatpak remote-add --if-not-exists flathub https://dl.flathub.org/repo/flathub.flatpakrepo

Verify the remote:

flatpak remotes

Fedora may also list its own fedora remote. The flathub line is the one GIMP needs.

Install the application:

sudo flatpak install flathub org.gimp.GIMP

Read the runtime and permission prompt before confirming. Flatpak will pull in the GNOME runtime and several extensions, which accounts for the larger download.

Run it:

flatpak run org.gimp.GIMP

To check the version without opening the interface:

flatpak run org.gimp.GIMP --version
flatpak info org.gimp.GIMP

System-wide versus per-user installs

The command above installs for every user on the machine. For a single-user laptop, a user-scope install avoids the need for sudo:

flatpak install --user flathub org.gimp.GIMP

The upstream GIMP download page shows the per-user form with a .flatpakref file, and notes that if GIMP does not show in menus after install, you can launch it with flatpak run org.gimp.GIMP//stable. On Fedora this seldom happens, because the desktop environment normally refreshes its application list after logout and login.

Choose system scope on shared workstations so everyone uses the same build. Choose user scope when you do not have admin rights or want the install to follow the home directory.

Keeping the Flatpak current

flatpak update

Run that weekly, or let GNOME Software or KDE Discover do it. To see what is stale:

flatpak remote-ls --updates

Method 3: Snap (Only if You Must)

The Snap Store publishes GIMP for Fedora, and installation requires snapd first. Fedora does not ship snapd as a default component, and it needs a classic-confinement symlink and a working AppArmor or SELinux interplay that add friction. Unless a team standard forces snaps, the first two methods are simpler and better supported on Fedora. Leave this one for edge cases.

Verifying a Healthy Install

Do not stop at “it opens.” A few quick checks save hours later.

  1. Open Help > About and confirm the version number.
  2. Create a 4000 by 3000 pixel image and apply a Gaussian blur. If this is painfully slow, see the performance section below.
  3. Open the Filters menu and check the Python-Fu and Script-Fu consoles if you rely on scripting. In GIMP 3 these menus changed, and some are not enabled in every build.
  4. Save a file as PNG and as JPEG, then reopen both. This confirms the image libraries work.
  5. Check Edit > Preferences > System Resources and look at the tile cache and thread settings.

From a terminal you can also confirm the binary linkage for the RPM:

ldd $(which gimp) | grep "not found"

No output means no missing libraries.

Wayland, X11 and Graphics Tablets

Fedora 45 defaults to Wayland on both GNOME and KDE. GIMP 3 handles Wayland far better than 2.10 did, but tablets remain the usual trouble spot. One guide notes that Wayland tablet support in GTK3-based GIMP keeps improving with each release, so reading the release notes for your version is wise.

Symptoms include pen pressure not registering, the pointer jumping, or an eraser tip behaving like a pen. Work through this order:

  1. Make sure the tablet is detected by the system.
libinput list-devices | grep -i -A5 tablet
  1. In GIMP, open Edit > Input Devices and set the tablet device mode to Screen rather than Disabled.
  2. If pressure still fails, log out and choose an X11 session at the login screen, if your desktop still offers one, and compare behavior. If it works on X11, the issue is on the Wayland input path rather than your configuration.

On a Wacom device, the libwacom package is normally present already. Missing it is rare on Fedora, but confirm with rpm -q libwacom.

Troubleshooting Common Problems

“No match for argument: gimp”

Usually a repository problem, not a missing package. Run:

sudo dnf clean all
sudo dnf makecache
dnf repolist

If the fedora and updates repositories are missing, a mirror issue or a broken .repo file is to blame. Check /etc/yum.repos.d/.

Dependency conflicts after upgrading from Fedora 44 or 43

Leftover packages from older releases can block installs. Try:

sudo dnf distro-sync
sudo dnf autoremove

Review the autoremove list before accepting it.

GIMP starts and instantly closes

Run it from the terminal and read the output:

gimp --verbose

For the Flatpak:

flatpak run --verbose org.gimp.GIMP

A broken plugin or corrupt preferences file is the usual cause. Rename the config directory to test a fresh profile. For the RPM it lives under ~/.config/GIMP/. For the Flatpak it lives under ~/.var/app/org.gimp.GIMP/config/.

mv ~/.config/GIMP ~/.config/GIMP.bak

If GIMP starts normally afterward, the problem was in your old settings. Move over only what you need.

Plugins from GIMP 2.10 do not appear

This is expected. GIMP 3 changed the plugin API, and older plugins need porting. Check whether the author has released a 3.x version, or look for a built-in replacement.

Menu entry missing after Flatpak install

Log out and back in. If it is still missing, confirm the exports path is set:

echo $XDG_DATA_DIRS

It should contain the Flatpak export directories. Fedora normally sets this, but a custom shell profile can override it.

Fonts look wrong or are missing in the Flatpak

The sandbox reads fonts from the host through a read-only mapping, but some custom font directories are not visible. Place fonts in ~/.local/share/fonts/, then run:

fc-cache -f

Restart GIMP afterward.

Slow or flickering canvas

Try turning off canvas-related options in Preferences > Display and check for a driver issue with glxinfo -B (from mesa-demos). If you recently updated a graphics driver, a reboot is usually the real fix.

Snap or Flatpak conflict warnings

Having both sets installed is not a conflict in itself, but file associations can point to the wrong one. Remove the version you do not use.

r00t is an experienced Linux enthusiast and technical writer with a passion for open-source software. With years of hands-on experience in various Linux distributions, r00t has developed a deep understanding of the Linux ecosystem and its powerful tools. He holds certifications in SCE and has contributed to several open-source projects. r00t is dedicated to sharing her knowledge and expertise through well-researched and informative articles, helping others navigate the world of Linux with confidence.

Related Posts