Discord provides voice, video, and text communication for gaming communities, study groups, and project collaboration teams. Whether you coordinate raid schedules with your guild, join development sprints with remote teammates, or run community events for hobbyist groups, Discord organizes conversations into topic-based channels with persistent chat history, supports screen sharing for collaboration, and integrates with games to display your current activity. By the end of this guide, you will have Discord installed and verified on Fedora, configured for audio and screen sharing, and able to troubleshoot common permission and detection issues.
Two installation methods serve different needs on Fedora. RPM Fusion integrates Discord directly into your system package management, synchronizing updates with your regular DNF workflow. Flatpak from Flathub manages Discord updates independently from system packages. This guide walks through both approaches, explains when to choose each based on your integration and security preferences, and covers post-install verification and common troubleshooting scenarios.
Choosing Between RPM Fusion and Flatpak
Before proceeding with installation, understanding the differences between installation methods helps you choose the right approach for your workflow:
| Method | Channel | Integration | Best For |
|---|---|---|---|
| RPM Fusion | Third-party repository | Full system access, DNF updates | Gamers needing activity detection, rich presence, and unrestricted file sharing |
| Flatpak | Flathub | Sandboxed, permission-based | Security-conscious users who prefer application isolation |
Choose RPM Fusion for full Discord integration with gaming features and system-wide file access. This method works especially well alongside other gaming tools like Steam and OBS Studio, where process detection and unrestricted filesystem access enhance functionality. Choose Flatpak when security isolation matters more than complete feature availability, or when you prefer keeping third-party applications separated from core system packages.
Method 1: Install Discord via RPM Fusion
Update Fedora Before Discord Installation
First, ensure all existing packages are up to date before installing Discord. This prevents potential conflicts with dependencies and maintains system stability.
sudo dnf upgrade --refreshThe command refreshes repository metadata and upgrades installed packages. You will see output similar to:
Last metadata expiration check: 0:00:12 ago on Wed Nov 27 10:30:00 2025. Dependencies resolved. Nothing to do. Complete!
Import RPM Fusion for Discord Installation
Next, Discord requires the RPM Fusion nonfree repository, which provides software unavailable in Fedora’s default repositories due to licensing restrictions. However, if you already enabled RPM Fusion during system installation or for other software, you can skip to the next section.
Import both RPM Fusion repositories with these commands:
sudo dnf install \
https://download1.rpmfusion.org/free/fedora/rpmfusion-free-release-$(rpm -E %fedora).noarch.rpm \
https://download1.rpmfusion.org/nonfree/fedora/rpmfusion-nonfree-release-$(rpm -E %fedora).noarch.rpmSuccessful installation produces output confirming the repository packages installed:
Last metadata expiration check: 0:01:23 ago on Wed Nov 27 10:32:00 2025. Dependencies resolved. ================================================================================ Package Architecture Version Repository Size ================================================================================ Installing: rpmfusion-nonfree-release noarch 43-1 @commandline 11 k Transaction Summary ================================================================================ Install 1 Package Total size: 11 k Installed size: 9.3 k Is this ok [y/N]: y Downloading Packages: Running transaction check Transaction check succeeded. Running transaction test Transaction test succeeded. Running transaction Preparing : 1/1 Installing : rpmfusion-nonfree-release-43-1.noarch 1/1 Verifying : rpmfusion-nonfree-release-43-1.noarch 1/1 Installed: rpmfusion-nonfree-release-43-1.noarch Complete!
Install Discord via DNF Command
Once RPM Fusion is enabled, install Discord through your standard package manager:
sudo dnf install discordDNF resolves dependencies and installs Discord. Typical output shows:
Last metadata expiration check: 0:02:15 ago on Wed Nov 27 10:35:00 2025. Dependencies resolved. ================================================================================ Package Architecture Version Repository Size ================================================================================ Installing: discord x86_64 0.0.116-1 rpmfusion-nonfree 89 M Transaction Summary ================================================================================ Install 1 Package Total download size: 89 M Installed size: 272 M Is this ok [y/N]: y Downloading Packages: discord-0.0.116-1.x86_64.rpm 3.2 MB/s | 89 MB 00:27 -------------------------------------------------------------------------------- Total 3.2 MB/s | 89 MB 00:27 Running transaction check Transaction check succeeded. Running transaction test Transaction test succeeded. Running transaction Preparing : 1/1 Installing : discord-0.0.116-1.x86_64 1/1 Running scriptlet: discord-0.0.116-1.x86_64 1/1 Verifying : discord-0.0.116-1.x86_64 1/1 Installed: discord-0.0.116-1.x86_64 Complete!
Method 2: Install Discord with Flatpak via Flathub
Alternatively, Flatpak comes pre-installed on Fedora and delivers containerized applications through the Flathub repository. The sandboxed environment restricts Discord’s access to system resources, enhancing security while maintaining core functionality. Furthermore, Flathub updates Discord independently from your system packages, eliminating dependency conflicts and providing access to the latest releases without waiting for distribution maintainers.
Ensure Flatpak is Installed on Fedora
If you have previously removed the Flatpak package manager, you can reinstall it using the following command:
sudo dnf install flatpakEnable Flathub for Discord Installation
Enable the Flathub repository before installing Discord. Note that you can skip this step if you previously added Flathub for other applications:
sudo flatpak remote-add --if-not-exists flathub https://flathub.org/repo/flathub.flatpakrepoInstall Discord via Flatpak Command
After enabling Flathub, install Discord from the repository:
flatpak install flathub com.discordapp.Discord -yFlatpak downloads the application and its runtime dependencies. You will see output similar to:
Looking for matches...
Required runtime for com.discordapp.Discord/x86_64/stable (runtime/org.freedesktop.Platform/x86_64/23.08) found in remote flathub
com.discordapp.Discord permissions:
ipc network pulseaudio wayland
x11 devices file access [1] dbus access [2]
system dbus access [3]
[1] xdg-download, xdg-pictures, xdg-videos
[2] org.freedesktop.Notifications, org.freedesktop.ScreenSaver,
org.freedesktop.secrets, org.kde.StatusNotifierWatcher
[3] org.freedesktop.UPower
ID Branch Op Remote Download
1. org.freedesktop.Platform.GL.default 23.08 i flathub 154.5 MB / 159.0 MB
2. org.freedesktop.Platform 23.08 i flathub 220.6 MB / 228.8 MB
3. com.discordapp.Discord stable i flathub 105.2 MB / 108.0 MB
Installation complete.
If the installation fails with “error: Unable to load summary from remote flathub: Cannot fetch summary from disabled remote,” the Flathub remote may be disabled. Re-enable it with
flatpak remote-modify --enable flathuband retry the installation command. This error commonly occurs after system upgrades that reset Flatpak remote configurations.
Launch Discord on Fedora
Launch Discord from Terminal
Following installation, launch Discord from the command line using the method that matches your installation:
RPM Fusion Installation
discordFlatpak Installation
flatpak run com.discordapp.DiscordDiscord opens in a new window and displays the login screen. The terminal shows minimal output as the application runs in the foreground.
Launch Discord from Application Menu
Most users prefer launching Discord through the graphical application menu rather than the terminal. Access Discord from your desktop environment:
- Press the Super key (Windows key) or click “Activities” in the top left corner.
- Type “Discord” in the search field.
- Click the Discord icon to launch the application.
Verify Discord Installation
After launching Discord successfully, confirm it installed correctly by checking the version number. The command varies by installation method:
RPM Fusion Version Check
dnf info discordAs a result, this command displays package information including the installed version:
Installed Packages Name : discord Version : 0.0.116 Release : 1 Architecture : x86_64 Size : 272 M Source : discord-0.0.116-1.src.rpm Repository : @System From repo : rpmfusion-nonfree Summary : All-in-one voice and text chat License : Proprietary Description : All-in-one voice and text chat for gamers that is free and secure.
Flatpak Version Check
flatpak info com.discordapp.DiscordSimilarly, Flatpak returns detailed application metadata:
Discord - Talk, play, hang out
ID: com.discordapp.Discord
Ref: app/com.discordapp.Discord/x86_64/stable
Arch: x86_64
Branch: stable
Version: 0.0.116
License: LicenseRef-proprietary
Origin: flathub
Collection: org.flathub.Stable
Installation: system
Installed: 272.9 MB
Runtime: org.freedesktop.Platform/x86_64/23.08
Sdk: org.freedesktop.Sdk/x86_64/23.08
Managing Discord Updates and Maintenance
Update Discord
Discord notifies users of available updates through in-app messages. However, you can also check for updates manually through the terminal. For tips on improving update performance, see the guide on increasing DNF speed on Fedora.
Update RPM Fusion Discord
For RPM installations, Discord updates integrate with system package management. Consequently, you can update Discord alongside other system packages:
sudo dnf upgrade --refreshUpdate Flatpak Discord
In contrast, Flatpak manages Discord updates independently from system packages. Therefore, update Discord and other Flatpak applications separately:
flatpak updateRemove Discord
Uninstall Discord using the method that matches your installation. Both approaches remove the application while preserving your user data in case you reinstall later.
Remove RPM Fusion Discord
Remove Discord installed through RPM Fusion:
sudo dnf remove discordRemove Flatpak Discord
Remove Discord installed through Flatpak. Include the --delete-data flag to also remove cached data and user settings:
flatpak remove --delete-data com.discordapp.DiscordOmit --delete-data if you want to preserve settings for future reinstallation.
Troubleshooting Common Discord Issues
Audio or Microphone Not Working
If Discord fails to detect your microphone or speakers, first verify PipeWire (Fedora’s default audio server) is running:
systemctl --user status pipewire pipewire-pulseBoth services should show as active:
● pipewire.service - PipeWire Multimedia Service
Loaded: loaded (/usr/lib/systemd/user/pipewire.service; enabled)
Active: active (running) since Wed 2025-11-27 10:30:00 EST
● pipewire-pulse.service - PipeWire PulseAudio
Loaded: loaded (/usr/lib/systemd/user/pipewire-pulse.service; enabled)
Active: active (running) since Wed 2025-11-27 10:30:00 EST
However, if either service is not running, restart them:
systemctl --user restart pipewire pipewire-pulseAdditionally, test audio devices in Discord settings under Voice & Video, and ensure no other application has exclusive audio device access.
For Flatpak installations, audio issues often stem from missing permissions. Check current permissions:
flatpak info --show-permissions com.discordapp.Discord | grep -E "pulseaudio|device"If Discord has proper audio access, you should see output similar to:
pulseaudio devices
Conversely, if the command returns no results or shows empty output, Discord lacks audio device access. Grant the necessary permissions:
flatpak override --user --device=all com.discordapp.DiscordAfterward, verify the permission was applied:
flatpak override --user --show com.discordapp.DiscordThe output should include the device permission:
[Context] devices=all;
Finally, restart Discord after changing permissions. The application should now detect your audio devices in Voice & Video settings.
Screen Sharing Not Available
Screen sharing requires specific permissions in sandboxed Flatpak environments. Therefore, ensure xdg-desktop-portal and xdg-desktop-portal-gtk (or your desktop environment’s portal backend) are installed:
sudo dnf install xdg-desktop-portal xdg-desktop-portal-gtkAlternatively, for GNOME users, install the GNOME portal backend instead:
sudo dnf install xdg-desktop-portal-gnomeOnce installed, verify the portal service is running:
systemctl --user status xdg-desktop-portalYou should see output indicating the service is active:
● xdg-desktop-portal.service - Portal service
Loaded: loaded (/usr/lib/systemd/user/xdg-desktop-portal.service; static)
Active: active (running) since Wed 2025-11-27 10:45:00 EST; 2min ago
Main PID: 12345 (xdg-desktop-por)
Tasks: 4 (limit: 19123)
Memory: 15.2M
CPU: 145ms
CGroup: /user.slice/user-1000.slice/user@1000.service/app.slice/xdg-desktop-portal.service
└─12345 /usr/libexec/xdg-desktop-portal
Otherwise, if the service is not running, start it manually:
systemctl --user restart xdg-desktop-portalRestart Discord after installing portal packages and confirming the service is running. Screen sharing prompts should now appear when you attempt to share.
Game Activity Not Showing
Game activity detection requires filesystem access to monitor running processes. The RPM Fusion installation provides unrestricted access and typically detects games automatically. However, Flatpak Discord runs sandboxed and cannot detect game activity by default.
To enable game detection in Flatpak Discord, you must grant broader filesystem access:
flatpak override --user --filesystem=home com.discordapp.DiscordSubsequently, verify the permission was applied:
flatpak override --user --show com.discordapp.DiscordThe output should include the filesystem permission:
[Context] filesystems=home;
Granting home directory access reduces sandboxing security benefits. Consider whether game activity visibility justifies this permission change, or use the RPM Fusion installation if game integration is essential.
Discord Fails to Launch
If Discord crashes immediately after launch or fails to start, check for conflicting processes or corrupted cache files. To diagnose the issue, start by running Discord from the terminal to capture error messages.
For RPM installations, launch with:
discordFor Flatpak installations:
flatpak run com.discordapp.DiscordCommon error output indicating cache corruption:
[0127/103000.123456:ERROR:database.cc(345)] Corrupted database [0127/103000.234567:FATAL:electron_main_delegate.cc(234)] Check failed: false. Trace/breakpoint trap (core dumped)
In addition, check system logs for RPM installations to identify underlying issues:
journalctl --user -xe | grep -i discordIf cache corruption is confirmed, clear Discord’s local data. For RPM installations:
rm -rf ~/.config/discordThen, verify the cache was cleared:
ls ~/.config/discord 2>&1You should see:
ls: cannot access '/home/user/.config/discord': No such file or directory
For Flatpak installations:
rm -rf ~/.var/app/com.discordapp.DiscordSimilarly, verify the cache was cleared by checking the directory no longer exists:
ls ~/.var/app/com.discordapp.Discord 2>&1You should see:
ls: cannot access '/home/user/.var/app/com.discordapp.Discord': No such file or directory
Following cache removal, restart Discord. The application will recreate its configuration files and you will need to log in again.
Conclusion
You configured Discord on Fedora using either RPM Fusion for DNF-managed updates or Flatpak for independent package management, verified audio device detection through PipeWire service checks, and applied portal permissions for screen sharing. Your installation supports voice channels, screen sharing, and game activity detection with the ability to troubleshoot permission issues through Flatpak overrides. For gaming setups, pair Discord with Steam and OBS Studio for streaming. Explore additional communication tools like Slack or Telegram for different collaboration needs.