This guide walks Fedora users through installing Slack on version 38 or newer, beginning with a quick system update to avoid dependency snags. After verifying your system is current, it shows how to download the official RPM from Slack’s website, install it via dnf—which automatically resolves libraries—launch the app to create its configuration folder, and highlights why Snap versions often fail due to sandbox restrictions. It also offers a flatpak alternative for those who need isolation, noting that this route consumes more disk space and starts up slower, so the author advises using the native package unless sandboxing is essential. Finally, the tutorial explains how to keep Slack updated with dnf upgrades, clean up old menu entries, and remove the application cleanly without leaving residual configuration files.

How to Install Slack on Fedora Linux (Fast & Reliable)

If you’re tired of waiting for that “Slack app” to launch after a messy install, this guide walks you through the cleanest ways to get Slack up and running on Fedora 38 or newer. You’ll learn which method is best for your distro version, why each command matters, and how to avoid common pitfalls.

1. Verify Your System

dnf check-update

Running a quick update before installing anything ensures you won’t hit dependency snags later. I’ve seen users try to pull Slack on an out‑of‑date system only to get “missing lib” errors, which are annoying and time‑consuming to fix.

2. Install via the Official RPM Package

1. Download the latest .rpm

   wget https://downloads.slack-edge.com/linux_releases/slack-desktop-4.35.0-amd64.rpm

Why this matters: The official package is signed and built for x86_64, so you avoid the extra dependency layers that come with other packaging formats.

2. Install with dnf

   sudo dnf install ./slack-desktop-4.35.0-amd64.rpm

Why this matters: dnf resolves dependencies automatically and keeps your package database tidy, unlike a manual extraction that can leave orphaned files.

3. Launch Slack

   slack

The first run will create the configuration folder (~/.config/Slack) and register the desktop entry, so you’ll see it in the app launcher from now on.

Observation: A friend once installed Slack via the Snap store on Fedora 38. The snap was stuck at “Pulling” for days, and when it finally appeared the binary couldn’t find libX11.so, because Snap’s confinement didn’t expose the needed libraries. Stick to RPMs unless you’re comfortable with flatpak or container tricks.

3. Install via Flatpak (If You Prefer Sandbox)

sudo dnf install flatpak
flatpak remote-add --if-not-exists flathub https://flathub.org/repo/flathub.flatpakrepo
flatpak install flathub com.slack.Slack

Why this matters: Flatpak isolates Slack from the rest of your system, which can be handy if you want to keep third‑party apps separate. The trade‑off is larger disk usage and a slower start‑up time compared to the native RPM.

Opinion: If you’re running a minimal Fedora install or care about disk space, the Flatpak route feels bloated. I’d recommend the RPM unless you have a specific sandboxing requirement.

4. Keep Slack Updated

The official channel is to reinstall the latest .rpm as it drops:

sudo dnf upgrade slack-desktop

This will fetch any newer releases from the repository that the package manager has indexed, ensuring you stay on the newest version without manually downloading again.

Scenario: A user once let Slack sit for weeks on an older release and then tried to install a new one. The old .rpm file lingered in /usr/share/applications, causing duplicate menu entries. Running dnf upgrade slack-desktop cleans up the old files automatically.

5. Optional: Remove Slack

If you ever need to cleanly uninstall it:

sudo dnf remove slack-desktop

And that’s it – no leftover config unless you deliberately keep the ~/.config/Slack directory.