Fedora

How to Install Slack on Fedora 44

Last updated Saturday, May 16, 2026 3:50 pm Joshua James 7 min read
Slack and Fedora logos side by side on a blue gradient background with messaging icons

Slack’s desktop client is not part of Fedora’s default repositories, and Slack’s Linux support matrix names Ubuntu LTS and RHEL rather than Fedora. For x86_64 systems, you can still install Slack on Fedora with Slack’s RHEL-compatible RPM package, a DNF repository that tracks that RPM, or the Flathub wrapper.

The DNF repository gives traditional Fedora Workstation installs package-manager updates, but the current Packagecloud repo disables RPM GPG checks. The direct RPM method lets you verify Slack’s package signature before installing, while Flatpak fits Atomic desktops and users who accept Flathub’s community wrapper.

Install Slack on Fedora

Pick one package source and keep the update and removal commands aligned with that source. Installing multiple Slack packages can leave duplicate launchers with different update paths.

MethodSourceUpdate BehaviorBest Fit
DNF repositorySlack PackagecloudDNF-managed updates; repo currently uses gpgcheck=0Traditional mutable Fedora systems that prioritize convenient updates
Direct RPMSlack DownloadsManual re-download and reinstallOffline installs or users who want to check Slack’s RPM signature first
FlatpakFlathub wrapperFlatpak updates through FlathubFedora Atomic desktops or users who prefer Flathub packaging and accept the wrapper source

Slack’s RPM and Flathub package currently target x86_64. If uname -m prints aarch64, arm64, or another architecture, use Slack in a browser at app.slack.com instead of forcing these desktop packages.

Confirm Fedora Uses x86_64

Check the CPU architecture before using the RPM or Flatpak paths:

uname -m
x86_64

Update Fedora Before Installing Slack

Refresh Fedora’s package metadata and apply pending updates before adding Slack. This helps DNF resolve dependencies from current repositories.

sudo dnf upgrade --refresh

These commands use sudo for administrative changes. If your account cannot run sudo commands yet, configure a Fedora sudo user first.

If the upgrade installs a new kernel, reboot before continuing so Fedora starts the updated kernel.

Install Slack with the DNF Repository

The Packagecloud repository keeps Slack available to DNF updates on mutable Fedora systems. The repository path still uses fedora/21, which is a Packagecloud layout detail rather than a Fedora release requirement.

Create the repository file with a copy-paste-stable printf command:

printf '%s\n' \
'[slack]' \
'name=Slack' \
'baseurl=https://packagecloud.io/slacktechnologies/slack/fedora/21/$basearch' \
'enabled=1' \
'gpgcheck=0' \
'repo_gpgcheck=0' \
'gpgkey=https://packagecloud.io/slacktechnologies/slack/gpgkey' \
'sslverify=1' \
'metadata_expire=300' | sudo tee /etc/yum.repos.d/slack.repo > /dev/null

The current Packagecloud repo publishes Slack packages but leaves package GPG verification disabled. Use the direct RPM method if your policy requires checking Slack’s RPM signature before installation.

Older repo snippets may include sslcacert=/etc/pki/tls/certs/ca-bundle.crt. Do not add that line on current Fedora releases; Fedora 44 uses a different CA bundle path, and DNF can use its default trust store without the extra setting.

Confirm DNF sees the new repository:

dnf repo list --all | grep -i slack
slack                                          Slack                                              enabled

Check the current package candidate from that repo:

dnf repoquery --repo=slack --latest-limit=1 --qf '%{name}-%{evr}.%{arch} %{repoid}' slack

Example output from current repository metadata:

slack-4.49.89-0.1.el8.x86_64 slack

Install Slack from the enabled repository:

sudo dnf install slack

Verify the package and launcher path after installation:

rpm -q slack
command -v slack

Example output:

slack-4.49.89-0.1.el8.x86_64
/usr/bin/slack

The el8 release suffix reflects Slack’s Enterprise Linux compatibility target. It is expected on Fedora because Slack reuses the same RPM build across compatible RPM-based desktops.

Install Slack with the Direct RPM

The direct RPM method downloads Slack’s current RPM from the official download page. It does not add the Packagecloud repo, so updates require downloading the next RPM and installing it again. That manual update path keeps the current file and signature check visible each time.

Resolve and download the current RPM URL with curl on Linux:

if mkdir -p ~/Downloads && cd ~/Downloads; then
  slack_rpm_url=$(curl -fsSL 'https://slack.com/downloads/instructions/linux?ddl=1&build=rpm&nojsmode=1' | grep -oE 'https://downloads\.slack-edge\.com/desktop-releases/linux/x64/[0-9.]+/slack-[^"<> ]+\.rpm' | head -n 1)
  if [ -n "$slack_rpm_url" ]; then
    slack_rpm_file=${slack_rpm_url##*/}
    if curl -fL -o "$slack_rpm_file" "$slack_rpm_url"; then
      printf 'Downloaded %s\n' "$slack_rpm_file"
    else
      rm -f "$slack_rpm_file"
      unset slack_rpm_file
      printf 'Slack RPM download failed\n' >&2
    fi
  else
    printf 'Slack RPM URL not found\n' >&2
  fi
else
  printf 'Cannot use ~/Downloads\n' >&2
fi

Continue only when the download block prints a filename. Keep the same terminal open so $slack_rpm_file still points to the RPM you just downloaded, then import Slack’s RPM signing key and check the package signature:

if [ -n "${slack_rpm_file:-}" ]; then
  curl -fsSLO https://slack.com/gpg/slack_pubkey_20251016.gpg
  gpg --show-keys --with-fingerprint slack_pubkey_20251016.gpg
  sudo rpm --import slack_pubkey_20251016.gpg
  rpm --checksig "$slack_rpm_file"
else
  printf 'Run the direct RPM download block first so %s is set\n' '$slack_rpm_file' >&2
fi

Relevant output includes Slack’s current signing-key fingerprint and a successful package check:

85C4 7808 639F CA46 57E1  5AB3 F3DD F357 1F28 FFDE
slack-4.49.89-0.1.el8.x86_64.rpm: digests signatures OK

Install the downloaded RPM with DNF so Fedora can resolve dependencies from its normal repositories:

if [ -n "${slack_rpm_file:-}" ]; then
  sudo dnf install ./"$slack_rpm_file"
else
  printf 'Run the direct RPM download block first so %s is set\n' '$slack_rpm_file' >&2
fi

DNF may still print a skipped OpenPGP checks warning for the local @commandline RPM, even after rpm --checksig "$slack_rpm_file" reports a valid Slack signature. Treat the earlier signature check as the package proof and continue only if DNF completes the install.

Verify the same package and launcher path used by the repository method:

rpm -q slack
command -v slack

Install Slack with Flatpak

Fedora Workstation, Silverblue, and Kinoite include Flatpak. Check whether the command is already available:

flatpak --version

If that command is missing on a trimmed mutable Fedora install, install Flatpak from Fedora’s repositories. Do not use this DNF command on Atomic desktops; standard Atomic editions already include Flatpak.

sudo dnf install flatpak

Add Flathub system-wide if it is not already configured:

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

Confirm Flathub is available at system scope:

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

Check the Slack Flatpak ref before installing:

flatpak remote-info --show-ref flathub com.slack.Slack
app/com.slack.Slack/x86_64/stable

Flathub currently labels this Slack listing as unverified and says the wrapper is not affiliated with or supported by Slack Technologies Inc. Use the direct RPM method when you need Slack’s own RPM package, or keep the Flatpak path when Flathub packaging is the tradeoff you want.

Flathub publishes Slack as a proprietary x86_64 app ref, but the wrapper is not a stronger security boundary. Current metadata grants network and IPC sharing, X11 or Wayland display access, PulseAudio access, all devices, and the Downloads folder.

flatpak remote-info --show-metadata flathub com.slack.Slack | grep -E '^(shared|sockets|devices|filesystems)='
shared=network;ipc;
sockets=x11;wayland;pulseaudio;fallback-x11;
devices=all;
filesystems=xdg-download;

Install the Flatpak app from Flathub:

sudo flatpak install flathub com.slack.Slack

Verify the installed Flatpak ref:

flatpak info --show-ref com.slack.Slack
app/com.slack.Slack/x86_64/stable

Launch Slack on Fedora

Slack needs an active graphical desktop session. Use the terminal command for your install method, or open the launcher from Fedora’s application menu.

Launch Slack from Terminal

For DNF repository or direct RPM installations, run the host launcher:

slack

For Flatpak installations, run the app ID:

flatpak run com.slack.Slack

Launch Slack from Activities

Search for “Slack” in Activities and open the launcher. On first launch, Slack asks you to sign in to a workspace or enter a workspace URL.

Example Fedora Activities search with the Slack application icon selected.
Example Activities search showing the Slack launcher; extra file matches and filenames vary by system.
Example Slack workspace sign-in window with the workspace URL field.
Example Slack sign-in window prompting for your workspace URL.

Update Slack on Fedora

Use the update command that matches your installation method. The DNF repository and Flatpak paths update through their package managers; the direct RPM path stays manual.

Update the DNF Repository Installation

Slack updates with normal Fedora package upgrades when the Packagecloud repository remains enabled:

sudo dnf upgrade --refresh

To check only Slack:

sudo dnf upgrade slack

Update the Direct RPM Installation

Direct RPM installations do not receive Packagecloud updates unless you later add the DNF repository. Download the current RPM from Slack again, verify the signature, and install the newer file with DNF:

if mkdir -p ~/Downloads && cd ~/Downloads; then
  slack_rpm_url=$(curl -fsSL 'https://slack.com/downloads/instructions/linux?ddl=1&build=rpm&nojsmode=1' | grep -oE 'https://downloads\.slack-edge\.com/desktop-releases/linux/x64/[0-9.]+/slack-[^"<> ]+\.rpm' | head -n 1)
  if [ -n "$slack_rpm_url" ]; then
    slack_rpm_file=${slack_rpm_url##*/}
    if curl -fL -o "$slack_rpm_file" "$slack_rpm_url"; then
      rpm --checksig "$slack_rpm_file" && sudo dnf install ./"$slack_rpm_file"
    else
      rm -f "$slack_rpm_file"
      printf 'Slack RPM download failed\n' >&2
    fi
  else
    printf 'Slack RPM URL not found\n' >&2
  fi
else
  printf 'Cannot use ~/Downloads\n' >&2
fi

Update the Flatpak Installation

Update only the Slack Flatpak with:

sudo flatpak update com.slack.Slack

To update every system-wide Flatpak app and runtime, run sudo flatpak update instead.

Troubleshoot Slack on Fedora

Use the checks below for the failure modes most likely to appear on current Fedora systems.

Slack Repository Fails with a CA Certificate Error

If an older repo file contains Fedora’s retired /etc/pki/tls/certs/ca-bundle.crt path, DNF may fail before it reaches the package list. Relevant output includes:

Curl error (77): Problem with the SSL CA cert
error adding trust anchors from file: /etc/pki/tls/certs/ca-bundle.crt

Open the repo file and remove the sslcacert= line, or recreate /etc/yum.repos.d/slack.repo with the repository command shown earlier.

DNF Cannot Find the Slack Package

Check whether the Slack repo is present and enabled:

dnf repo list --all | grep -i slack

If the command prints nothing, recreate the repository file. If the repo appears but package metadata looks stale, clean metadata and retry the install:

sudo dnf clean metadata
sudo dnf install slack

Direct RPM Signature Check Reports NOKEY

A fresh Fedora install does not know Slack’s RPM signing key yet, so rpm --checksig can report NOKEY or SIGNATURES NOT OK. If you still have $slack_rpm_file from the direct RPM download block, import Slack’s key and rerun the check against that file:

if [ -n "${slack_rpm_file:-}" ]; then
  curl -fsSLO https://slack.com/gpg/slack_pubkey_20251016.gpg
  sudo rpm --import slack_pubkey_20251016.gpg
  rpm --checksig "$slack_rpm_file"
else
  printf 'Run the direct RPM download block first so %s is set\n' '$slack_rpm_file' >&2
fi
slack-4.49.89-0.1.el8.x86_64.rpm: digests signatures OK

Flathub Remote Is Disabled or Missing

If Flatpak cannot read Flathub metadata, confirm the remote exists and is enabled:

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

Enable the remote again when it is listed but disabled:

sudo flatpak remote-modify --enable flathub

Slack Window Opens Blank or White

A blank Slack window can point to a graphics acceleration problem. Launch Slack once with GPU acceleration disabled to test that path:

slack --disable-gpu

For Flatpak installations, pass the same flag after the app ID:

flatpak run com.slack.Slack --disable-gpu

If this fixes the session, keep using the flag while you investigate the graphics driver or Wayland/XWayland behavior on that desktop.

Slack Tray Icon Is Missing on GNOME

GNOME does not show legacy tray icons without an AppIndicator extension. Install Fedora’s packaged extension and sign out and back in:

sudo dnf install gnome-shell-extension-appindicator

After logging back in, open the Extensions app and enable the AppIndicator extension if it is not active already.

Slack Audio or Microphone Does Not Work

Fedora uses PipeWire for desktop audio. Check the user sockets that provide PulseAudio-compatible audio to apps:

systemctl --user is-active pipewire.socket pipewire-pulse.socket
active
active

If either socket is inactive inside your graphical session, restart the user audio services:

systemctl --user restart pipewire pipewire-pulse wireplumber

For Flatpak installations, the current Slack manifest already exposes PulseAudio access. Recheck the Flatpak permission metadata before adding overrides.

Remove Slack from Fedora

Remove the package first, then clean up the source, signing key, or user data that belongs to the method you used.

Remove the Slack RPM Package

Use this command for both the DNF repository and direct RPM methods:

sudo dnf remove slack

Confirm the RPM package and launcher are gone:

rpm -q slack || true
hash -r
command -v slack || echo "slack command not found"
package slack is not installed
slack command not found

Remove the Packagecloud Repository

If you used the DNF repository method, remove the repo file and clean DNF metadata:

sudo rm -f /etc/yum.repos.d/slack.repo
sudo dnf clean metadata
dnf repo list --all | grep -i slack || echo "Slack repository is not configured"
Slack repository is not configured

Remove Slack’s RPM Signing Key

If you imported Slack’s signing key for the direct RPM method and no other Slack RPM source needs it, remove that exact key from the RPM database:

if rpm -q gpg-pubkey --qf '%{VERSION}\n' 2>/dev/null | grep -Eiq '^85c47808639fca4657e15ab3f3ddf3571f28ffde$'; then
  sudo rpmkeys --delete 85c47808639fca4657e15ab3f3ddf3571f28ffde
else
  echo "Slack signing key is not installed"
fi

Verify the key is gone:

rpm -q gpg-pubkey --qf '%{VERSION}\n' 2>/dev/null | grep -Eiq '^85c47808639fca4657e15ab3f3ddf3571f28ffde$' || echo "Slack signing key removed"
Slack signing key removed

Remove the Slack Flatpak

If you installed Slack with Flatpak, remove the system-wide app ref:

sudo flatpak uninstall com.slack.Slack

Confirm the system-scope app ref is no longer installed:

flatpak list --system --app --columns=application | grep -Fx com.slack.Slack || echo "NOT_INSTALLED"
NOT_INSTALLED

Remove Slack User Data

Package removal does not sign you out of Slack’s web service, but it can leave local workspace state, cached files, and Flatpak sandbox data in your home directory. Check for those paths first:

find "$HOME" -maxdepth 3 \( -path "$HOME/.config/Slack" -o -path "$HOME/.cache/Slack" -o -path "$HOME/.var/app/com.slack.Slack" \) -print

The following cleanup command permanently removes local Slack workspace state, cached files, and Flatpak sandbox data for this Linux account. Export or save anything you need before deleting these directories.

rm -rf "$HOME/.config/Slack" "$HOME/.cache/Slack" "$HOME/.var/app/com.slack.Slack"

Conclusion

Slack is ready on Fedora with the update path that matches your package source: DNF for the Packagecloud repo, manual signed RPM refreshes for direct downloads, or Flatpak updates through Flathub. For similar desktop communication tools, install Discord on Fedora or install Zoom on Fedora.

Follow LinuxCapable

Want more LinuxCapable guides in Google?

Add LinuxCapable as a preferred source so Google can show more of our fresh Linux tutorials in Top Stories and From your sources when relevant.

Add LinuxCapable as a preferred source on Google
Search LinuxCapable

Need another guide?

Search LinuxCapable for package installs, commands, troubleshooting, and follow-up guides related to what you just read.

Found this guide useful?

Support LinuxCapable to keep tutorials free and up to date.

Buy me a coffeeBuy me a coffee
Before commenting, please review our Comments Policy.
Formatting tips for your comment

You can use basic HTML to format your comment. Useful tags currently allowed in published comments:

You type Result
<code>command</code> command
<strong>bold</strong> bold
<em>italic</em> italic
<blockquote>quote</blockquote> quote block

Got a Question or Feedback?

We read and reply to every comment - let us know how we can help or improve this guide.

Let us know you are human: