How to Install Discord on Fedora 44

Discord keeps voice chat, screen sharing, text channels, and game activity in one desktop client, which is why many Fedora users install it alongside Steam, OBS Studio, and other gaming or community tools. To install Discord on Fedora, use RPM Fusion for a DNF-managed native package or Flathub for a Flatpak build with app-level permissions and independent updates.

The scope is the Discord desktop client, not a self-hosted Discord server or a Fedora community server. Discord’s official Linux download page currently offers RPM, DEB, tar.gz, and pkg.tar.zst packages, but the direct RPM is a standalone unsigned package and does not add a DNF repository. RPM Fusion and Flathub give Fedora users cleaner update and removal paths.

Choose How to Install Discord on Fedora

Both supported methods target x86_64 Fedora systems. Choose RPM Fusion when Discord needs normal desktop integration, game activity detection, and DNF updates. Choose Flatpak when you prefer Flathub’s packaging model and are comfortable with the current sandbox limitations.

The RPM Fusion package is available for Fedora 44 and Fedora 43 through RPM Fusion Nonfree Updates, and the Flathub method works across current Fedora desktop installs once Flathub is enabled.

Method	Source	Updates	Terminal Launcher	Best Fit
RPM Fusion	RPM Fusion Nonfree	DNF system updates	Discord	Gaming setups that need game activity, rich presence, and broader host integration
Flatpak	Flathub	Flatpak updates	flatpak run com.discordapp.Discord	Workstations that already use Flathub and can accept Flatpak feature limits

The RPM Fusion package name is lowercase discord, but its terminal launcher is uppercase Discord. Keep that distinction in mind when verifying or troubleshooting the native package.

Install Discord via RPM Fusion

Update Fedora Packages

Refresh Fedora’s package metadata and apply pending updates before adding Discord. This reduces dependency conflicts and gives DNF current repository data.

sudo dnf upgrade --refresh

A fully updated system returns a short result similar to this:

Updating and loading repositories:
Repositories loaded.
Nothing to do.
Complete!

Enable RPM Fusion Nonfree

Discord is not in Fedora’s default repositories. Enable RPM Fusion Free and Nonfree so DNF can install the package and pull related dependencies from the expected Fedora-compatible repositories. If RPM Fusion is already enabled for Steam, multimedia codecs, or another package, skip to the install command.

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

The $(rpm -E %fedora) expression expands to your installed Fedora release number, so the same command follows Fedora’s current release automatically. DNF may print an OpenPGP warning for the two local release RPMs from @commandline; that warning is expected during this repository-bootstrap step. Relevant lines include:

Package                    Arch   Version Repository        Size
Installing:
 rpmfusion-free-release    noarch 0:44-3  @commandline   5.6 KiB
 rpmfusion-nonfree-release noarch 0:44-3  @commandline   5.8 KiB

Transaction Summary:
 Installing:         2 packages

Warning: skipped OpenPGP checks for 2 packages from repository: @commandline
Complete!

Verify that the standard RPM Fusion repositories are enabled before installing Discord:

dnf repo list --enabled | grep -i rpmfusion

rpmfusion-free             RPM Fusion for Fedora 44 - Free
rpmfusion-free-updates     RPM Fusion for Fedora 44 - Free - Updates
rpmfusion-nonfree          RPM Fusion for Fedora 44 - Nonfree
rpmfusion-nonfree-updates  RPM Fusion for Fedora 44 - Nonfree - Updates

For a deeper repository walkthrough, use the dedicated guide to install RPM Fusion on Fedora.

Install Discord with DNF

Install the RPM Fusion Discord package with DNF:

sudo dnf install discord

DNF resolves the Discord package from RPM Fusion Nonfree Updates and lists the required Fedora dependencies before asking for confirmation. Relevant lines include:

Package                       Arch   Version                  Repository
Installing:
 discord                      x86_64 0:0.0.135-1.fc44         rpmfusion-nonfree-updates
Installing dependencies:
 dee                          x86_64 0:1.2.7-65.fc44          fedora
 libayatana-appindicator-gtk3 x86_64 0:0.5.94-5.fc44          fedora
 libunity                     x86_64 0:7.1.4-44.20190319.fc44 fedora

Transaction Summary:
 Installing:         9 packages

Install Discord with Flatpak via Flathub

The Discord Flathub package is verified and currently tracks Discord’s stable Linux release. Flathub labels it potentially unsafe because the app needs broad desktop permissions, and the package page notes that game activity, unrestricted file access, and rich presence do not work out of the box.

Check Flatpak on Fedora

Fedora Workstation includes Flatpak by default. On Fedora Server, minimal installs, or systems where Flatpak was removed, install it first:

sudo dnf install flatpak

Enable the Flathub Remote

Add Flathub at system scope so all local users can install and update the Discord Flatpak from the same remote:

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

Confirm that Flathub is available as a system remote:

flatpak remotes --columns=name,options | grep -E '^flathub[[:space:]]'

flathub  system

If Flathub exists but is disabled, re-enable it with sudo flatpak remote-modify --enable flathub, then repeat the remote check.

Install Discord from Flathub

Install Discord from the Flathub remote. The command uses sudo because the remote was added at system scope.

sudo flatpak install flathub com.discordapp.Discord

Review Flatpak’s permission summary before confirming the install. Current metadata identifies Discord as a stable x86_64 Flatpak using the Freedesktop runtime, and the verification workflow later in the article shows how to confirm the installed ref.

Launch Discord on Fedora

Launch Discord from Terminal

Use the launch command that matches your installation method.

RPM Fusion package:

Discord

Flatpak package:

flatpak run com.discordapp.Discord

Launching from a terminal keeps Discord attached to that terminal session. Close the app normally from the window, or press Ctrl+C in the terminal if you need to stop the foreground process.

Launch Discord from Activities

Open Activities, search for “Discord”, and select the Discord icon from the application grid.

Verify Discord Installation

Confirm the installed package before troubleshooting launch or update issues.

RPM Fusion package:

rpm -q discord
command -v Discord

discord-0.0.135-1.fc44.x86_64
/usr/bin/Discord

Flatpak package:

flatpak info com.discordapp.Discord | grep -E '^[[:space:]]*(ID|Ref|Arch|Branch|Version|Origin|Installation|Runtime):'

            ID: com.discordapp.Discord
           Ref: app/com.discordapp.Discord/x86_64/stable
          Arch: x86_64
        Branch: stable
       Version: 1.0.138
        Origin: flathub
  Installation: system
       Runtime: org.freedesktop.Platform/x86_64/25.08

Manage Discord Updates

Discord can also notify you inside the app, but package-manager updates keep the installed Fedora package or Flatpak ref aligned with the source you chose.

Update RPM Fusion Discord:

sudo dnf upgrade --refresh

To check only the Discord RPM package, use:

sudo dnf upgrade discord

If DNF updates feel slow on your connection, the Fedora guide to increase DNF speed on Fedora covers mirror and cache tuning separately.

Update Flatpak Discord:

sudo flatpak update com.discordapp.Discord

To update every system Flatpak app and runtime at once, use:

sudo flatpak update

Remove Discord from Fedora

Remove Discord with the package manager that installed it. Package removal does not sign you out of Discord on other devices, and it does not delete your Discord account.

Remove the RPM Fusion package:

sudo dnf remove discord

Verify the RPM package is gone:

rpm -q discord 2>/dev/null || echo "discord not installed"

discord not installed

If you enabled RPM Fusion only for Discord and no other RPM Fusion packages use it, remove the repository release packages too. Skip this cleanup when Steam, OBS Studio plugins, codecs, NVIDIA packages, or other RPM Fusion software still depends on those repositories.

sudo dnf remove rpmfusion-free-release rpmfusion-nonfree-release
sudo dnf clean metadata

Remove the Flatpak package:

sudo flatpak uninstall com.discordapp.Discord

Verify the Flatpak app ID is no longer installed:

flatpak list --app --columns=application | grep -Fx com.discordapp.Discord || echo "NOT_INSTALLED"

NOT_INSTALLED

Remove unused Flatpak runtimes only after reviewing the list Flatpak presents:

sudo flatpak uninstall --unused

Deleting local Discord data removes cached files, local settings, and saved sign-in state for this Fedora account. Export or back up anything you need before running the cleanup commands.

Check native Discord data paths before deleting them:

for path in "$HOME/.config/discord" "$HOME/.cache/discord"; do
  [ -e "$path" ] && printf '%s\n' "$path"
done

If those paths exist and you want a clean local reset, remove them:

rm -rf "$HOME/.config/discord" "$HOME/.cache/discord"

For the Flatpak package, remove the current user’s sandbox data only when you do not need local settings or cached sign-in state:

rm -rf "$HOME/.var/app/com.discordapp.Discord"

Troubleshoot Common Discord Issues

Audio or Microphone Not Working

Discord uses Fedora’s PipeWire audio stack. Check the user services from a graphical desktop session:

systemctl --user is-active pipewire pipewire-pulse

active
active

If either service is inactive while you are signed in to the desktop, restart the audio services and then reopen Discord:

systemctl --user restart pipewire pipewire-pulse

For Flatpak installs, verify the current permissions before adding overrides. Relevant lines from the current Flathub package include PulseAudio, PipeWire runtime access, and broad device access:

flatpak info --show-permissions com.discordapp.Discord

[Context]
shared=ipc;network;
sockets=pcsc;pulseaudio;wayland;x11;
devices=all;
filesystems=xdg-download;xdg-pictures:ro;xdg-videos:ro;xdg-run/pipewire-0;

If a previous local override removed those permissions, reset user overrides and restart Discord:

flatpak override --user --reset com.discordapp.Discord

Screen Sharing Prompt Does Not Appear

Fedora Workstation uses XDG Desktop Portal to broker screen sharing prompts on Wayland. Minimal installs and non-GNOME spins may need the matching portal backend installed.

GNOME Workstation:

sudo dnf install xdg-desktop-portal xdg-desktop-portal-gnome

KDE Plasma:

sudo dnf install xdg-desktop-portal xdg-desktop-portal-kde

After attempting screen sharing, check the user portal service:

systemctl --user status xdg-desktop-portal --no-pager

The service can be inactive before an application requests a portal. If Discord still shows no prompt after the backend package is installed, sign out and back in so the desktop session reloads portal services cleanly.

Game Activity or Rich Presence Missing in Flatpak

Flathub documents game activity detection as unavailable for the Discord Flatpak because the sandbox cannot scan running host processes. Use the RPM Fusion package when game activity detection is essential.

File attachments from outside the default Flatpak paths are a separate limitation. If you need Discord to attach files from more of your home directory, grant home-directory access and then restart Discord:

flatpak override --user --filesystem=home com.discordapp.Discord

Home-directory access weakens the sandbox boundary. Use it only when the file attachment workflow matters more than keeping Discord limited to the default download, pictures, and videos paths.

Discord Fails to Launch

Start by confirming which package is installed, then launch Discord from the terminal to capture the error text.

RPM Fusion package:

rpm -q discord
Discord

Flatpak package:

flatpak info com.discordapp.Discord
flatpak run com.discordapp.Discord

If Discord launches from one method but not the other, keep troubleshooting within that package source. For RPM Fusion, check the user journal for recent Discord messages:

journalctl --user -xe | grep -i discord

If the terminal output points to a corrupted local profile or stale cache, close Discord and clear only the data path for the method you use. The removal workflow includes separate native and Flatpak data cleanup commands.

Conclusion

Discord is now installed on Fedora through either RPM Fusion for DNF-managed desktop integration or Flathub for Flatpak-managed updates. RPM Fusion is the better default for gaming features such as game activity detection, while Flatpak remains useful for users who prefer Flathub packages and understand the sandbox tradeoffs. For a broader Fedora gaming setup, pair Discord with Steam on Fedora and OBS Studio on Fedora. For other chat clients, compare Slack on Fedora or Telegram on Fedora.