A team invite is waiting, the meeting starts soon, and Linux package advice has somehow turned into a debate about repositories. You do not need that detour. On a supported Ubuntu system, Slack offers two practical paths: the verified Snap or Slack’s own 64-bit .deb package.

Choose one. Slack explicitly advises against keeping its Snap and another Linux package installed at the same time, and that is good operational advice: one app, one update owner, one place to troubleshoot.

First, make sure this Ubuntu release is still invited

Terminalbash
lsb_release -ds
dpkg --print-architecture

Two lines that prevent a frustrating false start

  • At the time of this review, Slack lists Ubuntu LTS 22.04 or newer as supported. Slack revises system requirements twice each year, so check the linked requirements page if you are reading this later.

  • The direct Ubuntu download is a 64-bit DEB. amd64 is the expected Debian architecture label for a conventional x86-64 Ubuntu installation.

  • Do not interpret “a snap can run here” as “Slack supports this operating-system release.” The application lifecycle and the package system are separate questions.

  • Slack still labels its Linux desktop app beta. That matters when a feature behaves differently from macOS, Windows, or the browser.

Choose the update story you want to live with

  • Choose Snap when you want the short install command and Snap-managed automatic refreshes. Ubuntu desktop normally includes snapd, and the Slack publisher account in the Snap Store is verified.

  • Choose the official DEB when your organization manages APT packages or you prefer Slack’s native Ubuntu package. Download it only from Slack’s Linux download page.

  • Do not install both. Duplicate launchers, separate data locations, and two update mechanisms make ordinary problems needlessly ambiguous.

The Snap path is intentionally uneventful

Terminalbash
sudo snap install slack

Risk level: caution. Review the command before running it.

What you just handed to Snap

  • sudo authorizes a system package change; read the package name before approving it.

  • Without an explicit channel, snap install selects the publisher’s default stable channel.

  • Snap refreshes installed packages automatically by default. That convenience also means update timing belongs to the Snap refresh policy rather than an APT upgrade run.

  • Slack’s current official command does not require --classic; do not copy that broader-confinement flag from an old tutorial.

Terminalbash
snap info slack
snap list slack

The receipt worth keeping

  • snap info lets you confirm the publisher and available channels before treating a similarly named package as authentic.

  • snap list slack reports the installed version, revision, tracking channel, and publisher; it does not contact your workspace or sign you in.

  • For a managed workstation, discuss refresh scheduling with the administrator instead of pinning an old collaboration client indefinitely.

The DEB path starts in a browser, not a guessed URL

Open Slack’s Linux download page, choose the 64-bit DEB, and let the browser save the file. The filename contains a version and changes over time, which is why hard-coding an old download URL or an old filename ages badly.

Terminalbash
cd ~/Downloads
ls -lh slack-desktop-*.deb
dpkg-deb --info ./slack-desktop-*.deb | sed -n "1,25p"

Pause at the package boundary

  • The glob should resolve to exactly the file you just downloaded. If several Slack DEBs are present, replace it with the exact filename rather than letting a command select multiple files.

  • dpkg-deb --info reads metadata without installing the package. Confirm the package name, architecture, and version look plausible.

  • A familiar filename is not provenance. The trusted starting point is Slack’s HTTPS download page, not a third-party mirror or copied attachment.

Terminalbash
sudo apt install ./slack-desktop-VERSION-amd64.deb

Risk level: caution. Review the command before running it.

Why APT is doing this job

  • apt install ./file.deb installs the local package and resolves declared dependencies through configured Ubuntu repositories.

  • VERSION is a placeholder, not literal shell input. Type ./slack-desktop- and use Tab completion to insert the real filename safely.

  • This avoids the old dpkg -i followed by a dependency-repair ritual. APT can coordinate both parts in one transaction.

  • Slack’s DEB may configure an APT source for later updates. Review changes under /etc/apt/sources.list.d/ if your organization controls repositories.

Launch once, then verify the package—not your memory

Terminalbash
slack

The handoff to your workspace

  • You can also open Slack from Ubuntu’s application grid. The terminal is useful only when the graphical launch silently fails.

  • Workspace authentication commonly moves through your default browser and back to the desktop app. A blocked custom-protocol handoff can leave the sign-in apparently stranded in the browser.

  • Do not paste access tokens or workspace secrets into a diagnostic command. Slack’s normal sign-in flow should not require that.

Terminalbash
if snap list slack >/dev/null 2>&1; then
  snap list slack
else
  dpkg-query -W -f="${Package} ${Version} ${Architecture}\n" slack-desktop
fi

One package manager should answer

  • The branch checks the Snap first; if it is absent, dpkg-query asks APT’s package database for slack-desktop.

  • A package record proves installation, not that notifications, audio, video, or workspace policy are working.

  • If both package managers report Slack, remove the copy you did not intend to maintain before debugging desktop integration.

When Slack opens but the desktop still feels wrong

  • No launcher appears: log out and back in after installation, or launch slack once from a terminal and read the first error instead of reinstalling immediately.

  • Browser sign-in will not return: allow the browser to open the Slack application link and check whether another Slack package captured the protocol handler.

  • Notifications are missing: confirm Slack’s own notification preferences, Ubuntu notification permissions, Do Not Disturb, and the selected output device.

  • Calls or screen sharing fail: first compare the current Linux app and OS against Slack’s requirements, then test the same workspace in a supported Chrome or Firefox browser. Desktop environment, display protocol, portal, and workspace policy can all change the result.

  • Only one network fails: Slack uses persistent HTTPS/WebSocket connectivity. A proxy, TLS inspection appliance, VPN, or firewall policy can break the app while installation remains perfectly healthy.

Updates follow the path you chose

Terminalbash
# Snap installation
sudo snap refresh slack

# Official DEB installation
sudo apt update
sudo apt install --only-upgrade slack-desktop

Risk level: caution. Review the command before running it.

Keep the ownership line clear

  • snap refresh slack asks Snap to refresh Slack immediately; routine Snap refreshes are automatic unless an administrator has changed policy.

  • apt update refreshes repository metadata, while --only-upgrade refuses to install slack-desktop if it is not already present.

  • Slack’s supported app and OS versions change over time. A successful package-manager command does not override an ended Slack support lifecycle.

Remove the app without casually erasing your local state

Terminalbash
# Snap installation
sudo snap remove slack

# Official DEB installation
sudo apt remove slack-desktop

Risk level: caution. Review the command before running it.

Uninstalling and forgetting are separate decisions

  • Package removal takes away the application but can leave user configuration or a Snap snapshot behind, depending on package-manager behavior and local policy.

  • Slack’s troubleshooting instructions identify ~/.config/Slack for the direct-download app. Deleting it signs the local app out and discards local preferences; back it up first if you are unsure.

  • Do not recursively delete hidden directories copied from a forum post. Confirm the package type, exact path, and consequence before removing user data.

Useful neighboring Ubuntu notes

Sources checked for this rewrite