If you have ever dealt with a missing application in Fedora’s default repos or waited weeks for an upstream update to land in DNF, you already know the frustration. Learning how to install Flatpak on Fedora 44 solves that problem directly by giving you access to thousands of sandboxed apps that update independently of your system. This guide walks you through every step, from verifying your system state to installing apps, managing permissions, and fixing the errors that trip up most beginners. Whether you are running Fedora 44 Workstation, a KDE spin, or a minimal server image, these instructions cover all of them.

I have spent the last 10 years managing Fedora systems in production environments, from developer workstations to containerized CI/CD servers. The single most common setup mistake I still see is users who install Flatpak but never add the Flathub remote, then wonder why they cannot find any apps. This guide fixes that before it happens to you.

What Is Flatpak and Why Use It on Fedora 44

Fedora 44 ships with Linux Kernel 6.19 and GNOME 50, and it has dropped X11 entirely in favor of a Wayland-only desktop. That is a meaningful change because some apps in the traditional RPM repository have not fully caught up with Wayland compatibility yet. Flatpak fills that gap.

Flatpak is a universal application packaging system for Linux. It bundles each app with the specific runtime libraries it needs, so the app runs in isolation from your host system. That isolation is called a sandbox, and it serves two purposes: it keeps apps from breaking each other, and it limits what each app can access on your machine.

Here is why Flatpak makes particular sense on Fedora 44 specifically:

• Fedora releases happen roughly every 6 months. App updates on Flathub ship the same day developers push them upstream.
• Wayland-native Flatpak builds are available for apps that still lag on RPM.
• Flatpak is the packaging format Fedora itself uses for its curated app bundles.
• Apps installed via Flatpak survive major Fedora version upgrades without breaking.

Flatpak vs. RPM vs. Snap on Fedora 44

Before you install everything from Flathub, it helps to know where each format belongs:

The practical rule: use RPM for system tools, development dependencies, and anything that needs deep OS access. Use Flatpak for desktop apps, media players, browsers, and creative software. Avoid Snap on Fedora entirely since it has no official support and the daemon integration is clunky.

Prerequisites

Before running a single command, confirm you have these in place:

• Fedora 44 installed (Workstation, KDE Plasma, Server, or any official spin)
• sudo privileges on your user account
• Active internet connection (Flatpak pulls runtimes remotely during installation)
• Terminal access (GNOME Terminal, Kitty, Konsole, or SSH on a server)
• At least 2 GB free disk space for the Flatpak runtime and your first app
• Basic comfort running commands in a terminal

If you are on a headless Fedora 44 server via SSH, skip the GNOME Software sections. All CLI steps in this guide work identically over SSH.

Step 1: Update Your Fedora 44 System

What this does: Syncs your local package metadata with Fedora’s mirrors and installs any pending updates before you add new software.

Why this matters: Running an outdated system before installing Flatpak can cause DNF dependency conflicts. On Fedora 44, there may also be pending kernel or glibc updates. Installing Flatpak on top of an un-patched system risks library version mismatches later.

Open your terminal and run:

sudo dnf update -y

Expected output (abbreviated):

Last metadata expiration check: 0:02:14 ago on Mon 04 May 2026.
Dependencies resolved.
...
Complete!

If the update includes a kernel upgrade, reboot before continuing:

sudo reboot

After rebooting, log back in and re-open your terminal. You are now on a clean, fully updated base.

Step 2: Check If Flatpak Is Already Installed

What this does: Queries the system for an existing Flatpak binary.

Why this matters: Fedora 44 Workstation, Silverblue, and Kinoite all ship Flatpak pre-installed. If you reinstall it blindly, DNF will complete without error, but you risk resetting your Flatpak configuration, including any remotes you already added. Checking first takes 3 seconds and avoids that problem.

Run:

flatpak --version

If Flatpak is installed, you will see output like:

Flatpak 1.15.8

Skip to Step 4 (Enable Flathub). You do not need to reinstall.

If Flatpak is not installed, the terminal returns:

bash: flatpak: command not found

This is common on Fedora 44 Server, Fedora IoT, or a custom minimal install. Continue to Step 3.

Check Existing Remotes While You Are Here

flatpak remotes

If this returns output showing fedora but no flathub, that is the most common misconfiguration I see. The fedora remote only contains RPM-to-Flatpak conversions, not the full Flathub catalog. You will fix that in Step 4.

Step 3: Install Flatpak on Fedora 44 via DNF

What this does: Installs the Flatpak runtime, its CLI tools, and required libraries from Fedora’s official repositories.

Why this matters: Flatpak in Fedora’s repos is always the version tested and verified for compatibility with your specific kernel and glibc. Installing it from a third-party source introduces unnecessary risk.

Run:

sudo dnf install flatpak -y

DNF resolves dependencies automatically. You will see output similar to:

Dependencies resolved.
=====================================
 Package          Architecture   Version
 flatpak          x86_64         1.15.8-1.fc44
 ...
Installing: 1 package(s)
Complete!

Now verify the installation succeeded:

flatpak --version

You should see the version number. If the binary is still not found after a successful DNF install, your current shell session needs refreshing:

exec bash

Or simply log out and log back in to reload your PATH variable.

Step 4: Enable Flathub Repository on Fedora 44

This is the most important step in the entire guide. Flatpak without Flathub is like a package manager with no packages.

What Flathub is: The primary community-maintained repository for Flatpak apps. It hosts over 2,500 apps, including software that never gets packaged for Fedora’s RPM repos. Without Flathub, you can only install from the fedora remote, which is a small subset.

Method 1: Command Line (Recommended for All Users)

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

Breaking down each part of this command:

• flatpak remote-add: Registers a new repository in your Flatpak config
• --if-not-exists: Makes the command safe to re-run. If Flathub already exists, no error is thrown and nothing is overwritten
• flathub: The local name you assign to this remote
• The URL: Points to Flathub’s .flatpakrepo file, which includes the GPG signing key, repo location, and metadata needed for verification

By default, this registers Flathub system-wide, meaning all users on the machine can install from it. If you want to scope it to your account only, add the --user flag:

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

After running the command, confirm Flathub is active:

flatpak remotes

Expected output:

Name     Options
fedora   system,oci
flathub  system

Seeing flathub in this list means you are fully configured and ready to install apps.

Method 2: GNOME Software GUI (Workstation Only)

If you prefer not to use the terminal for this step:

1. Open Settings on Fedora 44 GNOME 50
2. Navigate to Privacy and Security
3. Find Third-Party Repositories and toggle Flathub to On
4. Close Settings and relaunch GNOME Software

Why this works: Fedora’s Settings panel runs the same flatpak remote-add command under the hood, plus it imports the GPG key automatically. The result is identical to the CLI method.

Step 5: Install Your First Flatpak Application

Now the practical part. You will install an app two ways: through the GUI and through the terminal.

Installing via GNOME Software (GUI)

Open GNOME Software from your activities overview. Search for any application, such as VLC or GIMP. You will notice each app shows a source label beneath it. Apps tagged with dl.flathub.org are Flatpak builds from Flathub. Click the app and hit Install.

GNOME Software handles everything from here, including downloading the required runtime for that app.

Installing via Terminal (Recommended)

Step 1: Search for the app

flatpak search vlc

Output:

Name   Description                    Application ID        Version   Branch   Remotes
VLC    Media player and streamer      org.videolan.VLC      3.0.21    stable   flathub

The Application ID (org.videolan.VLC) is how Flatpak uniquely identifies every app. You need this ID for installation, running, and uninstalling.

Why the Application ID matters: If two remotes carry the same app, specifying only the app name causes an ambiguous prompt that can stall automated scripts. Always use the full reverse-domain ID in commands.

Step 2: Install by Application ID

flatpak install flathub org.videolan.VLC

You will see Flatpak download the app plus its required runtime (such as org.freedesktop.Platform). On first install, the runtime download can be 150-300 MB. After that, all subsequent apps using the same runtime reuse the cached copy.

Confirm the prompts with y when asked.

Step 3: Launch the app

flatpak run org.videolan.VLC

Or find it in your application menu like any other installed software.

Step 6: Manage Your Flatpak Applications

Update All Flatpak Apps

flatpak update

Why run this separately from dnf update: Flatpak and DNF are completely independent update systems. Running only sudo dnf update leaves your Flatpak apps on whatever version was current at install time. Many security patches ship exclusively through Flatpak updates.

Run this weekly, or enable the built-in systemd timer that ships with Fedora 44:

sudo systemctl enable --now flatpak-system-update.timer

This auto-updates all system Flatpak apps in the background without any manual intervention.

List Installed Apps

flatpak list --app

The --app flag filters out runtimes and shows only the apps you intentionally installed. Without it, the output includes every shared runtime, which makes the list hard to read.

Uninstall an App

flatpak uninstall org.videolan.VLC

Clean Up Unused Runtimes

flatpak remove --unused

Why this matters: After uninstalling apps, their shared runtimes remain on disk. Each runtime is 150-500 MB. Running this command monthly prevents your /var partition from quietly filling up over time.

Step 7: Manage Flatpak Sandbox Permissions

Flatpak sandboxes each app by default, which means apps cannot read your home directory, access USB devices, or use the microphone unless explicitly permitted.

On Fedora 44, which ships with SELinux in enforcing mode, that sandbox adds a meaningful security layer. However, legitimate apps sometimes need access you have not granted yet, and they will fail silently or show confusing errors when that happens.

Install Flatseal, the best GUI tool for managing Flatpak permissions:

flatpak install flathub com.github.tchx84.Flatseal

Launch it from your app menu. Flatseal shows every installed app alongside its current permissions. You can toggle access to the filesystem, network, devices, and D-Bus services without editing config files by hand.

Key permissions to review for any app you install:

• filesystem=home or filesystem=host: Grants broad file system access, which weakens the sandbox significantly
• socket=system-bus: Allows the app to talk to system services
• share=network: Controls internet access

The rule of thumb: grant only what the app genuinely needs for the features you actually use.

Troubleshooting Common Flatpak Issues on Fedora 44

Error 1: “No Remote Refs Found” or Empty Search Results

Cause: Flathub was never added, or it was added at user level but you are running system-level commands (or vice versa).

Fix:

flatpak remotes --show-details

Confirm Flathub appears and its URL is https://dl.flathub.org/repo. If it is missing, re-run the remote-add command from Step 4.

Error 2: Flatpak Apps Not Showing in GNOME Activities

Cause: On Fedora 44 with GNOME 50, desktop entries are registered from XDG_DATA_DIRS at login. Your current session does not see apps installed after you logged in.

Fix: Log out and log back in. If you want to avoid a full logout, run:

update-desktop-database ~/.local/share/applications/

On Wayland sessions (which is all sessions on Fedora 44), a full logout is the reliable fix since the GNOME shell reload shortcut does not work on pure Wayland.

Error 3: GPG Verification Error During Install

Cause: The .flatpakrepo file downloaded with corrupted or incomplete data, leaving an invalid GPG key in the remote config.

Fix:

flatpak repair

This command re-checks all objects in the local Flatpak repository, re-pulls anything corrupt, and regenerates checksums. Run it without sudo for user-level installs, or with sudo for system-wide.

Error 4: App Launches But Shows No Window on Wayland

Cause: Fedora 44 dropped X11 entirely. Some older Flatpak apps still default to XWayland mode and fail to initialize correctly on a pure Wayland compositor like GNOME 50.

Fix: Launch the app with an explicit backend override:

flatpak run --env=GDK_BACKEND=wayland org.example.AppName

If the app uses Qt instead of GTK, try:

flatpak run --env=QT_QPA_PLATFORM=wayland org.example.AppName

If that still does not work, check the app’s Flathub page for known Wayland issues or open a bug report with the app’s maintainer.

Error 5: Disk Space Fills Up After Several App Installs

Cause: Multiple runtimes accumulate, especially if you installed and uninstalled several apps over time.

Fix: Run a cleanup:

flatpak remove --unused
flatpak repair

Check current disk usage by Flatpak:

du -sh /var/lib/flatpak/
du -sh ~/.local/share/flatpak/

If the numbers are large, review your installed runtimes with flatpak list (without --app) and remove any runtime version no longer needed.

Configure Flatpak on Fedora 44 for Long-Term Use

A clean install is the starting point, not the finish line. Here are the practices that separate well-maintained Fedora systems from the ones that accumulate clutter over time.

Prefer Flatpak for these app categories:

• Web browsers (Firefox, Chromium, Brave)
• Media players and editors (VLC, Kdenlive, Audacity)
• Communication apps (Slack, Telegram, Signal)
• Creative tools (GIMP, Inkscape, Blender)

Keep using DNF for these:

• Development tools (gcc, git, python3, nodejs)
• System utilities (htop, tmux, rsync)
• Server software (nginx, postgresql, nodejs for headless use)
• Anything that needs direct access to kernel APIs or low-level hardware

Mixing both formats strategically gives you the best of both worlds: rock-solid system internals managed by DNF and always-current desktop apps delivered through Flatpak.

Congratulations! You have successfully installed Flatpak. Thanks for using this tutorial for installing Flatpak on your Fedora 44 Linux system. For additional or useful information, we recommend you check the official Flatpak website.