Package Details: slack-desktop-wayland 4.41.98-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: 8
Popularity: 0.88
First Submitted: 2023-01-06 06:10 (UTC)
Last Updated: 2024-12-06 04:35 (UTC)

Dependencies (14)

Required by (0)

Sources (2)

Latest Comments

1 2 3 4 Next › Last »

ingvij commented on 2025-01-21 17:19 (UTC)

I'm re-installing slack-desktop-wayland in a fresh install and it seems like it still requires xwayland. I'm wondering if it should be added as a dependency or if there's something missing in the config - the intent isn't fully clear.

ajacocks commented on 2024-10-15 15:03 (UTC)

Anyone else unable to resize the window? Mine seems stuck at a small size, but not blurriness or other issues.

heylookmatt commented on 2024-09-18 17:55 (UTC) (edited on 2024-09-18 19:52 (UTC) by heylookmatt)

Starting today (weird because there hasn't been an update in a bit) I'm seeing the same behavior CommanderRedYT described, even when using the .desktop file. It's not an issue with just this package, I also tried with the slack-desktop package and I see the same behavior. The issue appears to be the ozone flags. If I remove --enable-features=UseOzonePlatform --ozone-platform=wayland it works (albeit in xwayland), otherwise it crashes. I've tried downgrading and wiping my ~/.config/Slack directory and I still see the same problem, which is irritating. Could be something got screwed up local to my machine, or there's some other issue that's just breaking Wayland support on slack

EDIT tried again a few hours later and it's fine :eyeroll: just goes to show, if you leave a problem alone long enough it'll fix itself :eyes:

mrpeabody commented on 2024-08-29 23:40 (UTC) (edited on 2024-08-29 23:42 (UTC) by mrpeabody)

4.40.120 is out:

cat slack-desktop-4.40.120-amd64.deb | b2sum

gives b2ac591f6abaa4fa37508c9dcce5eee382affbbde7612b1191c830ad95b51127d407657c1d0503cdb54032113b57c78785da8db0ac6e44bf469aa3273b50e1bd -

cspeck-aai commented on 2024-07-09 03:45 (UTC) (edited on 2024-07-12 06:16 (UTC) by cspeck-aai)

@CommanderRedYT it needs to be started using the Desktop entry. If you want to avoid that you could try using dex /usr/share/applications/slack.desktop as suggested in the wiki or $(grep Exec /usr/share/applications/slack.desktop | cut -d= -f2). Latest is running fine for me.

CommanderRedYT commented on 2024-07-08 07:58 (UTC)

Unfortunately with the latest version when running /usr/bin/slack there is no output for a while and then there is information about deprecated crash dumps. Nothing really happens after that, so it probably crashes instantly.

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.

1 2 3 4 Next › Last »