Package Details: slack-desktop-wayland 4.43.51-1

Git Clone URL: https://aur.archlinux.org/slack-desktop-wayland.git (read-only, click to copy)
Package Base: slack-desktop-wayland
Description: Slack Desktop (Beta) for Linux with Wayland Support
Upstream URL: https://slack.com/downloads
Licenses: custom
Conflicts: slack-desktop, slack-electron
Provides: slack-desktop
Submitter: cspeck-aai
Maintainer: cspeck-aai
Last Packager: cspeck-aai
Votes: 9
Popularity: 1.09
First Submitted: 2023-01-06 06:10 (UTC)
Last Updated: 2025-04-17 05:25 (UTC)

Dependencies (14)

Required by (0)

Sources (2)

Latest Comments

« First ‹ Previous 1 2 3 4 5 Next › Last »

cspeck-aai commented on 2024-06-02 23:47 (UTC)

Some of the intermediate Slack versions have been skipped because screen sharing tests failed, 4.38.125 appears to work though the process remains clunky.

Humpie commented on 2024-05-31 10:50 (UTC)

@CommanderRedYT If Slack is blurry in Gnome with Wayland (similar to how to fix Chrome), you can add the "--disable-features=WaylandFractionalScaleV1" option to the .desktop file.

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}.slack.com/ssb/signin_redirect/fallback.

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.

« First ‹ Previous 1 2 3 4 5 Next › Last »