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 while running in a sandboxed environment. 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.
Choose Your Discord Installation Method
Before proceeding with installation, understanding the differences between installation methods helps you choose the right approach for your workflow:
| Method | Channel | Updates | Integration | Best For |
|---|---|---|---|---|
| RPM Fusion | RPM Fusion Nonfree | Via DNF system upgrades | Full system access | Gamers needing activity detection, rich presence, and unrestricted file sharing |
| Flatpak | Flathub | Independent via Flatpak | Sandboxed, permission-based | Security-conscious users who prefer application isolation |
For most users, the RPM Fusion method is recommended because it provides full Discord integration with gaming features, automatic updates through your regular system maintenance, and unrestricted access to filesystem and process detection. 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 System
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 --refresh flag forces DNF to update repository metadata before checking for upgrades. When your system is already current, you will see output similar to:
Updating and loading repositories: Repositories loaded. Nothing to do. Complete!
Import RPM Fusion Repositories
Next, Discord requires the RPM Fusion nonfree repository, which provides software unavailable in Fedora’s default repositories due to licensing restrictions. If you already enabled RPM Fusion during system installation or for other software, you can skip to the next section. For a complete guide on RPM Fusion configuration, see how to install RPM Fusion on Fedora.
Import both RPM Fusion repositories with this command:
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.rpmThe
$(rpm -E %fedora)expression automatically expands to your current Fedora release number (such as 43 or 44), ensuring this command works across Fedora versions without modification.
Successful installation produces output confirming both repository packages installed:
Updating and loading repositories: Repositories loaded. Package Arch Version Repository Size Installing: rpmfusion-free-release noarch 43-1 @commandline 5.6 KiB rpmfusion-nonfree-release noarch 43-1 @commandline 5.8 KiB Transaction Summary: Installing: 2 packages Total size of inbound packages is 23 KiB. Need to download 0 B. After this operation, 11 KiB extra will be used (install 11 KiB, remove 0 B). Running transaction [1/4] Verify package files 100% | 0.0 B/s | 2.0 B | 00m00s [2/4] Prepare transaction 100% | 2.0 KiB/s | 2.0 B | 00m00s [3/4] Installing rpmfusion-nonfree-rele 100% | 1.2 MiB/s | 7.4 KiB | 00m00s [4/4] Installing rpmfusion-free-release 100% | 448.5 KiB/s | 7.2 KiB | 00m00s Warning: skipped OpenPGP checks for 2 packages from repository: @commandline Complete!
Install Discord via DNF
Once RPM Fusion is enabled, install Discord through your standard package manager:
sudo dnf install discordDNF resolves dependencies and installs Discord from the RPM Fusion nonfree-updates repository. Review the package details and confirm the installation when prompted:
Updating and loading repositories: RPM Fusion for Fedora 43 - Nonfree - U 100% | 7.1 KiB/s | 31.8 KiB | 00m04s RPM Fusion for Fedora 43 - Nonfree 100% | 15.9 KiB/s | 94.8 KiB | 00m06s Repositories loaded. Package Arch Version Repository Size Installing: discord x86_64 0.0.118-1.fc43 rpmfusion-nonfree-updates 79.8 MiB Transaction Summary: Installing: 1 package Total size of inbound packages is 80 MiB. Need to download 80 MiB. After this operation, 264 MiB extra will be used (install 264 MiB, remove 0 B). Is this ok [y/N]: y
Method 2: Install Discord with Flatpak via Flathub
Alternatively, Flatpak 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 often providing access to newer releases before they reach RPM Fusion.
Verify Flatpak Installation
Flatpak comes pre-installed on Fedora Workstation. If you have previously removed the Flatpak package manager or are using a minimal Fedora installation, reinstall it with:
sudo dnf install flatpakEnable Flathub Repository
Enable the Flathub repository before installing Discord. This step is required only once, and you can skip it if you previously added Flathub for other applications:
sudo flatpak remote-add --if-not-exists flathub https://dl.flathub.org/repo/flathub.flatpakrepoThe --if-not-exists flag prevents errors if Flathub is already configured. Verify the remote was added successfully:
flatpak remote-listYou should see Flathub listed:
flathub system
Install Discord via Flatpak
After enabling Flathub, install Discord from the repository:
flatpak install flathub com.discordapp.Discord -yFlatpak downloads the application and its runtime dependencies. The -y flag automatically confirms the installation. You will see progress output showing the required runtime and Discord itself being downloaded:
Looking for matches...
Required runtime for com.discordapp.Discord/x86_64/stable (runtime/org.freedesktop.Platform/x86_64/25.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 25.08 i flathub 164.2 MB / 169.0 MB
2. org.freedesktop.Platform 25.08 i flathub 232.1 MB / 240.5 MB
3. com.discordapp.Discord stable i flathub 113.3 MB / 116.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. Press Ctrl+C to close Discord when running from the terminal.
Launch Discord from Applications Menu
Most users prefer launching Discord through the graphical application menu rather than the terminal. Access Discord from your desktop environment:
- Open Activities and search for “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. This verification step confirms the package manager recognizes the installation and helps when troubleshooting issues later.
RPM Fusion Version Check
dnf info discordThis command displays package information including the installed version:
Installed packages Name : discord Epoch : 0 Version : 0.0.118 Release : 1.fc43 Architecture : x86_64 Installed size : 264.1 MiB Source : discord-0.0.118-1.fc43.src.rpm Repository : @System From repository: rpmfusion-nonfree-updates Summary : All-in-one voice and text chat URL : https://discordapp.com/ License : Proprietary Description : Linux Release for Discord, a free proprietary VoIP application Vendor : RPM Fusion
Flatpak Version Check
flatpak info com.discordapp.DiscordFlatpak returns detailed application metadata including the runtime version:
ID: com.discordapp.Discord
Ref: app/com.discordapp.Discord/x86_64/stable
Arch: x86_64
Branch: stable
Collection: org.flathub.Stable
Download: 113.3 MB
Installed: 286.1 MB
Runtime: org.freedesktop.Platform/x86_64/25.08
Sdk: org.freedesktop.Sdk/x86_64/25.08
Manage Discord Updates
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. You can update Discord alongside other system packages during your regular maintenance:
sudo dnf upgrade --refreshTo update only Discord without upgrading other packages:
sudo dnf upgrade discordUpdate Flatpak Discord
In contrast, Flatpak manages Discord updates independently from system packages. Update Discord and other Flatpak applications separately:
flatpak updateTo update only Discord:
flatpak update com.discordapp.DiscordRemove 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 discordDNF automatically removes unused dependencies if you have clean_requirements_on_remove enabled (the default behavior). Your Discord configuration and cache files remain in ~/.config/discord/ for potential reinstallation.
Remove 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. After removal, you can also clean up unused Flatpak runtimes to free disk space:
flatpak uninstall --unusedTroubleshoot 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)
● pipewire-pulse.service - PipeWire PulseAudio
Loaded: loaded (/usr/lib/systemd/user/pipewire-pulse.service; enabled)
Active: active (running)
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.
Fix Flatpak Audio Permissions
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:
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;
Restart Discord after changing permissions. The application should now detect your audio devices in Voice & Video settings.
Screen Sharing Not Available
Screen sharing on Fedora requires the XDG Desktop Portal, which Flatpak applications use to request screen capture permission. Fedora Workstation includes these components by default, but minimal installations may need them added manually.
For GNOME users (Fedora Workstation default), install the GNOME portal backend:
sudo dnf install xdg-desktop-portal xdg-desktop-portal-gnomeFor KDE Plasma users (Fedora KDE Spin):
sudo dnf install xdg-desktop-portal xdg-desktop-portal-kdeOnce 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)
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, the issue often stems from corrupted cache files or conflicting processes. To diagnose the problem, launch Discord from the terminal to capture error messages.
For RPM installations:
discordFor Flatpak installations:
flatpak run com.discordapp.DiscordWatch the terminal output for error messages. Common error output indicating cache corruption includes references to “Corrupted database” or “Check failed” messages. In addition, check system logs for RPM installations:
journalctl --user -xe | grep -i discordClear Discord Cache
If cache corruption is confirmed, clear Discord’s local data. This action removes your cached files and settings, requiring you to log in again.
For RPM installations:
Warning: The following command permanently deletes Discord’s configuration and cache. You will need to log in again and reconfigure your settings after restarting Discord.
rm -rf ~/.config/discordVerify 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.DiscordVerify the cache was cleared:
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 installed Discord on Fedora using either RPM Fusion for DNF-managed updates with full system integration or Flatpak for independent, sandboxed package management. Both methods deliver a fully functional Discord client for voice channels, text chat, and video calls. You can now verify your installation with package manager queries, configure audio through PipeWire, enable screen sharing via XDG Desktop Portal, and troubleshoot common permission issues with 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.