Arch Linux User Repository

Please, don't ask for add lsb-release as dependency. In Arch Linux this package is not needed to run Slack Desktop.

And before asking for any other dependency as make or patch or whatever, please read the wiki.

Consider using a downgraded version of electron (say electron 15, haven't had many issues with it). With the most recent version of electron (16 at time of writing), I am now only having issues if I enable the WebRTCPipeWireCapturer feature :\ Guess I can't have screensharing

I am also seeing the segmentation fault trying to run on wayland with 4.23.0

Most recent update (4.23.0) breaks if trying to run it in pure wayland mode (with WebRTC enabled).

$ slack --enable-features=UseOzonePlatform --ozone-platform=wayland
Initializing local storage instance
(electron) Sending uncompressed crash reports is deprecated and will be removed in a future version of Electron. Set { compress: true } to opt-in to the new behavior. Crash reports will be uploaded gzipped, which most crash reporting servers support.
[2167056:1215/105110.561823:ERROR:object_proxy.cc(642)] Failed to call method: org.freedesktop.DBus.Properties.Get: object_path= /org/freedesktop/portal/desktop: org.freedesktop.DBus.Error.InvalidArgs: No such interface “org.freedesktop.portal.FileChooser”
[2167056:1215/105110.561846:ERROR:select_file_dialog_impl_portal.cc(243)] Failed to read portal version property
[2167110:1215/105110.591670:ERROR:gpu_init.cc(457)] Passthrough is not supported, GL is egl, ANGLE is
[2167110:1215/105110.596663:ERROR:sandbox_linux.cc(376)] InitializeSandbox() called with multiple threads in process gpu-process.
[2167056:1215/105110.672593:ERROR:browser_main_loop.cc(269)] Gtk: gtk_widget_add_accelerator: assertion 'GTK_IS_ACCEL_GROUP (accel_group)' failed
[2167056:1215/105110.672640:ERROR:browser_main_loop.cc(269)] Gtk: gtk_widget_add_accelerator: assertion 'GTK_IS_ACCEL_GROUP (accel_group)' failed
zsh: segmentation fault (core dumped)  slack --enable-features=WebRTCPipeWireCapturer,UseOzonePlatform --ozone-platform=wayland

edit: might have been an inconsistent state in my system, it seems it launches okay... albeit only sometimes. If anyone else runs into something, do tell.

Got this upon start of 4.22.0-1:

$ slack
[3324:1125/082737.173451:ERROR:process_singleton_posix.cc(419)] readlink failed: Not a directory (20)
[3324:1125/082737.173557:ERROR:process_singleton_posix.cc(256)] readlink(~/.config/Slack/SingletonLock) failed: Not a directory (20)
[3324:1125/082737.173582:ERROR:process_singleton_posix.cc(256)] readlink(~/.config/Slack/SingletonLock) failed: Not a directory (20)
[3324:1125/082737.173590:ERROR:process_singleton_posix.cc(280)] Failed to create ~/.config/Slack/SingletonLock: Not a directory (20)
[3324:1125/082737.173602:ERROR:process_singleton_posix.cc(419)] readlink failed: Not a directory (20)
[3324:1125/082737.173610:ERROR:process_singleton_posix.cc(256)] readlink(~/.config/Slack/SingletonLock) failed: Not a directory (20)

I only see ~/.config/Slack which is a file instead of a directory. Deleting that file allows starting, though. Sounds like an improper migration to me.

@FizzyGalacticus, I can't reproduce this error, but I have a ~/$USER/.config/Slack. Maybe try manually making ~/$USER/.config/Slack/local-settings.json. My version of that file just contains {"lastElectronVersionLaunched":"14.0.0","electronFeatureOverrides":[]}, but I would try it with an empty file first. If that doesn't work, try the slack-electron package instead.

Ever since I updated to the lastest version, I'm receiving the following errors:

Initializing local storage instance
(electron) Sending uncompressed crash reports is deprecated and will be removed in a future version of Electron. Set { compress: true } to opt-in to the new behavior. Crash reports will be uploaded gzipped, which most crash reporting servers support.
Couldn't save to /$USER/.config/Slack/local-settings.json: ENOENT: no such file or directory, open '/$USER/.config/Slack/local-settings.json.24822100'
Error: ENOENT: no such file or directory, mkdir '/$USER/.config/Slack/storage'
    at Object.mkdirSync (node:fs:1324:3)
    at w._init (/usr/lib/slack/app.asar/dist/main.bundle.js:342:4874)
    at new w (/usr/lib/slack/app.asar/dist/main.bundle.js:342:4188)
    at new b (/usr/lib/slack/app.asar/dist/main.bundle.js:342:34641)
    at Tx (/usr/lib/slack/app.asar/dist/main.bundle.js:188:26694)
    at configureStore (/usr/lib/slack/app.asar/dist/main.bundle.js:188:27177)
    at U2 (/usr/lib/slack/app.asar/dist/main.bundle.js:188:50506)
    at B2 (/usr/lib/slack/app.asar/dist/main.bundle.js:188:51419) {
  errno: -2,
  syscall: 'mkdir',
  code: 'ENOENT',
  path: '/$USER/.config/Slack/storage'
}
[85690:0100/000000.746763:ERROR:vaapi_wrapper.cc(1104)] vaQuerySurfaceAttributes failed, VA error: invalid parameter
[85690:0100/000000.746796:ERROR:vaapi_wrapper.cc(1051)] FillProfileInfo_Locked failed for va_profile VAProfileH264Main and entrypoint VAEntrypointVLD
[85690:0100/000000.746808:ERROR:vaapi_wrapper.cc(1104)] vaQuerySurfaceAttributes failed, VA error: invalid parameter
[85690:0100/000000.746816:ERROR:vaapi_wrapper.cc(1051)] FillProfileInfo_Locked failed for va_profile VAProfileH264High and entrypoint VAEntrypointVLD

Note: I replaced my actual username with $USER

It looks like it's trying to create files/directories at the root of the filesystem instead of in my home directory.

Searching for these errors has lead me absolutely nowhere, and I'm hoping someone may have a solution? I looked at the main.bundle.js file in hopes I could manually update to just put in my home dir, but since it's minified js, it's very difficult to follow.

There's a 4.20 update and they seem to have decided it is no longer beta (at least in their url).
New pkgver: 4.20.0
New sha256: b08207389246837536ea769425d458411c08dc6802ffaae9249092e387461ce5
New url: https://downloads.slack-edge.com/releases/linux/{pkgver}/prod/x64 /${pkgname}-${pkgver}-amd64.deb"

Hi. I am having an issue with the font on code blocks - it looks like I am missing a font, but I am not sure which one. Does anyone know?

Hi, when I start or receive a slack call, the audio settings don't pick up an input (tried multiple microphones). Other applications don't run into this issue (zoom, google meet, chime, to name a few). Has anyone seen this issue before and resolved it? I'm wondering if I need to configure pulseaudio in anyway for this specific application to work with my audio inputs?