Package Details: slack-desktop-wayland 4.36.134-3

Git Clone URL: (read-only, click to copy)
Package Base: slack-desktop-wayland
Description: Slack Desktop (Beta) for Linux with Wayland Support
Upstream URL:
Licenses: custom
Conflicts: slack-desktop, slack-electron
Provides: slack-desktop
Submitter: cspeck-aai
Maintainer: cspeck-aai
Last Packager: cspeck-aai
Votes: 3
Popularity: 0.35
First Submitted: 2023-01-06 06:10 (UTC)
Last Updated: 2024-01-12 01:02 (UTC)

Dependencies (14)

Required by (0)

Sources (2)

Latest Comments

1 2 3 Next › Last »

CommanderRedYT commented on 2024-03-07 09:25 (UTC)

I noticed weird behavior with the .desktop file. I have Gnome Shell with Wayland enabled. My laptop has both Intel UHD Graphics and a NVIDIA GPU (however, i configured everything so that it should run on the integrated intel graphics). My monitors are all 4K. When I use the Slack listed in the search of gnome (so the .desktop file), everything looks somewhat fuzzy. However, if I start the application via command line (/usr/bin/slack), everything looks crystal clear.

The exec-line in the .desktop file is the following:

Exec=/usr/bin/slack --disable-gpu-compositing --enable-features=UseOzonePlatform --ozone-platform=wayland --enable-features=WebRTCPipeWireCapturer --enable-features=WaylandWindowDecorations -s %U

cspeck-aai commented on 2024-01-12 01:06 (UTC)

The multiple instances issue + login loops appear to be caused by using the system Electron and the application archive. This has been reverted and we will now use the compiled executable package which includes the vendor's Electron version.

marvas commented on 2024-01-11 13:21 (UTC) (edited on 2024-01-11 13:22 (UTC) by marvas)

It is true that the problem with the repeated login requests sometimes occurred before. I don't know how, but for me the problem was always solved after a while (application restart or system reboot does not work, just wait a few hours after a successful login).

But gnuruzzi describes a problem, which is definitly specific to this repository: The system is no longer able to detect the instance of Slack. Instead, a new process is opened each time a login request is triggered. This makes the existing problem worse and can freeze your complete system.

Just try the following:

  • Open the slack app

  • Open the slack app again

Old behavior (without system electron): The Slack app is recognized and displayed in the foreground.

New behavior: Two Slack apps are running at the same time.

CommanderRedYT commented on 2024-01-11 08:58 (UTC)

I downgraded to commit 14865e45c5406fcb1dbba6c12db37722e9dc5755 and I was logged in again (before downgrade i wasnt)

CommanderRedYT commented on 2024-01-11 08:51 (UTC)

Latest version for me works to login with the thing mentioned by cspeck-aai, but I get logged out after some time (<1d). Yesterday I logged myself into the application, now it wants me to do that again..

cspeck-aai commented on 2024-01-10 01:36 (UTC)

gnuruzzi & katsuoryuu that problem isn't specific to this package you need to get the Slack login key.

If you are signed into those workspace in the browser, get it from https://{yourworkspace}

This package and method works for me.

gnuruzzi commented on 2024-01-09 10:19 (UTC)

Latest version goes into a dead loop of logging in and opening an un-authenticated client again and again and again ...

katsuoryuu commented on 2024-01-09 01:21 (UTC)

This latest version causes me to go into a dead-loop where it opens slack, fails to login and slack calls (for some reason) 3 times to the browser to login, and just continues this loop. It seems that the browser cannot catch the existing running instance.

sewer56 commented on 2024-01-04 10:05 (UTC)

Can confirm it works under electron28 and electron27; under the current setup.

Sure the flow is convoluted but thankfully, at least it works. It could be worse (see: Discord). Haha

cspeck-aai commented on 2024-01-04 00:13 (UTC)

@sewer56 Turns out I was getting those errors too, although in the background on my system (Nvidia proprietary drivers + Gnome) it was recovering and loading anyway.

I've pushed a change that disables GPU acceleration in the embedded Electron Chrome browser and this has made these errors stop.

Note that it appears to take three clicks after you click "Share screen" in a huddle, the Slack "Share your screen" appears with the xdg-desktop-portal over the top:

  1. select from xdg-desktop-portal, it disappears
  2. select from Slack "Share your screen", xdg-desktop-portal reappears
  3. select from xdg-desktop-portal, it disappears, a control bar appears and sharing starts

This convoluted flow doesn't appear in other situations, e.g. sharing in Firefox via Jitsi Meet. You should complain to the makers of Slack if you want this flow fixed.

If you (or anyone else) wants to play around further with the flags or electron version you can do so like this:

SLACK_ELECTRON_EXEC=electron28 SLACK_WAYLAND_FLAGS="..." /usr/bin/slack

I can confirm it's working with current electron (electron27) and electron28.