I run the Slack standalone application on an Ubuntu 16.04 machine which has two sound devices: the built-in sound, and a USB headset. I don't use a desktop environment, but I am running X and pulseaudio is running (as set up by default on Ubuntu). I want all applications (Chrome, Slack, Skype, etc.) to use the USB headset for sound when it's plugged in. Until recently, this is the way it worked. I don't remember doing anything special to configure this. I just used the PulseAudio volume control application (pavucontrol) the first time (and only the first time) I used sound in the application: when the application appears in the “Playback” or “Recording” tab, switch it from “Built-in audio” to the USB headset, and the setting sticks for subsequent times. Since a few days ago, this no longer works for Slack. Slack always the built-in audio even when the USB headset is plugged in. To use the headset for a Slack voice call, I need to wait until the call has started, then go to the “Playback” tab of PA Volume Control and switch the device (oddly, it also controls the recording direction). I think the change happened when I upgraded from slack-desktop version 3.3.8 to 3.4.0. I use the package source https://packagecloud.io/slacktechnologies/slack/debian/ which is automatically set up by the slack-desktop package. The recent update to 4.0.0 didn't fix this. How can I get Slack to always prefer the USB headset when it's present? I don't mind how it's done, but I want it to happen automatically. Losing audio for a few seconds at the beginning of a call while I fiddle with settings is not acceptable. And I want to keep using the standalone application for this, not a browser tab.

Since today, when doing apt-get update, I am receiving

Warning: GPG error: https://packagecloud.io/slacktechnologies/slack/debian  jessie InRelease: Sub-process /usr/bin/sqv returned an error code (1), error message is: Signing key on DB085A08CA13B8ACB917E0F6D938EC0D038651BD is not bound:
           primary key   because: No binding signature at time 2024-12-17T17:27:20Z   because: Policy rejected non-revocation signature (PositiveCertification) requiring collision resistance   because: SHA1 is not considered secure since 2013-02-01T00:00:00Z
Error: The repository 'https://packagecloud.io/slacktechnologies/slack/debian  jessie InRelease' is not signed.

/etc/apt/sources.list.d/slacktechnologies_slack.list contains:

deb https://packagecloud.io/slacktechnologies/slack/debian/  jessie main
deb-src https://packagecloud.io/slacktechnologies/slack/debian/  jessie main

Trying to follow the old instructions of:

curl -s https://packagecloud.io/install/repositories/slacktechnologies/slack/script.deb.sh  | sudo bash

did not solve the issue. As a side note, the package was updated not so long ago: 26 days. https://packagecloud.io/slacktechnologies/slack?page=1 Does anyone have any update on this?

curl -F file=@"/home/siva/Downloads/heap2.hprof.gz" -F channels="xxxxxxxxxxxxxxxx" -H "Authorization: Bearer xxxxxxxxxxxxx" https://slack.com/api/files.upload My file size is 150 mb Iam not able send this file to slack Using api

I have a following JSON file:

{
  "blocks": [
    {
      "type": "section",
      "text": {
        "type": "mrkdwn",
        "text": "Success: ondrejdolezal93's workflow () in  ()\n- Fix update version ( by ondrejdolezal93)"
      }
    }
  ]
}

I am trying to send a message using Slack webhook with use of curl. My command is like following:

curl -X POST -H 'Content-type: application/json' --data @message.json $SLACK_WEBHOOK_URL

The reply from curl is: no_text Please, what am I doing wrong? JSON is formatted according to Slack API documentation.

On Manjaro, I have installed com.slack.Slack in version 4.23.0 through flatpak. Now, when I try to share a screen, I unexpectedly get a "Screen Share" popup that appears to be coming from Gnome. I expect to not see that at all but that I can select the app / screen directly from the underlaying slack Share Screen popup. The additional Screen Share popup would be fine, yet it also does not react on clicks. I cannot Cancel, Share and cannot even a select a screen nor an entire screen. How to properly enable screen share?

I am using Slack for Linux (Beta) 4.16 on Ubuntu 20.04 and experience very slow and sluggish typing sometimes (not always, hard to reproduce). I have 40GB of RAM and quite a powerful laptop, and it happens even when my CPU is barely working and I still have like 80% of RAM free. Disabling the spell checker as some have suggested doesn't help. Does anybody else have this problem?

I'm observing similar issues mentioned here https://unix.stackexchange.com/questions/79364/operation-in-dev-shm-causes-overflow I've 32GB, Ubuntu 20.04, Kernel 5.14, AMD RYZEN, 25GB of swap. >Linux FP-LSC0727L 5.14.0-1048-oem #55-Ubuntu SMP Mon Aug 8 14:58:10 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux > tmpfs 6,0G 6,0G 0 100% /dev/shm After reaching 100% of tmpfs all electron based apps crashed. And I am not able to run it again, but when resize the /dev/shm > sudo mount -o remount,size=10G /dev/shm I can get it back to work for a while, until the additional mem got used. I've tried to downgrade kernel to 5.13 and upgrade to >uname -a Linux FP-LSC0727L 5.15.0-46-generic #49~20.04.1-Ubuntu SMP Thu Aug 4 19:15:44 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux It didn't helped at all. The logs from slack when it crashed > /var/log/syslog seems like >Aug 23 11:21:53 FP-LSC0727L slack.desktop: [4357:0823/112153.759453:ERROR:command_buffer_proxy_impl.cc(94)] ContextResult::kFatalFailure: AllocateAndMapSharedMemory failed Aug 23 11:21:53 FP-LSC0727L slack.desktop: [4357:0823/112153.759551:ERROR:broker_posix.cc(46)] Received unexpected number of handles Aug 23 11:21:53 FP-LSC0727L slack.desktop: [4357:0823/112153.759581:ERROR:command_buffer_proxy_impl.cc(94)] ContextResult::kFatalFailure: AllocateAndMapSharedMemory failed Aug 23 11:21:53 FP-LSC0727L slack.desktop: [4357:0823/112153.759666:ERROR:broker_posix.cc(46)] Received unexpected number of handles Aug 23 11:21:53 FP-LSC0727L slack.desktop: [4357:0823/112153.759694:ERROR:command_buffer_proxy_impl.cc(94)] ContextResult::kFatalFailure: AllocateAndMapSharedMemory failed Aug 23 11:21:53 FP-LSC0727L slack.desktop: ...MORE SIMILAR LINES... Aug 23 11:21:53 FP-LSC0727L slack.desktop: [4357:0823/112153.761103:ERROR:command_buffer_proxy_impl.cc(94)] ContextResult::kFatalFailure: AllocateAndMapSharedMemory failed Aug 23 11:21:53 FP-LSC0727L slack.desktop: [4357:0823/112153.761230:ERROR:broker_posix.cc(46)] Received unexpected number of handles Aug 23 11:21:53 FP-LSC0727L slack.desktop: [4357:0823/112153.761275:ERROR:command_buffer_proxy_impl.cc(94)] ContextResult::kFatalFailure: AllocateAndMapSharedMemory failed Aug 23 11:21:53 FP-LSC0727L slack.desktop: [4357:0823/112153.761389:ERROR:broker_posix.cc(46)] Received unexpected number of handles > google-chrome -v [28114:28114:0823/120623.888519:ERROR:platform_shared_memory_region_posix.cc(217)] Creating shared memory in /dev/shm/.com.google.Chrome.XQhry3 failed: No space left on device (28) [28114:28153:0823/120623.888743:ERROR:platform_shared_memory_region_posix.cc(217)] Creating shared memory in /dev/shm/.com.google.Chrome.vldHe2 failed: No space left on device (28) [28114:28114:0823/120623.888758:ERROR:platform_shared_memory_region_posix.cc(217)] Creating shared memory in /dev/shm/.com.google.Chrome.1QE8A4 failed: No space left on device (28) Trace/breakpoint trap (core dumped) slack 4.27.156 64 latest/stable slack✓ -

I am using debian 10 ... slack desktop Production 4.9.1 64-bit I am getting a black screen when I tried to share in screen in a call. I am getting this in the log: [09/30/20, 16:41:14:528] info: [SCREENS] (T359LF935) Available screens: -- | ----- | ------ | - | --- | ----------- | -------- id | width | height | x | y | scaleFactor | rotation -- | ----- | ------ | - | --- | ----------- | -------- 33 | 1920 | 1080 | 0 | 0 | 2 | 0 35 | 960 | 539 | 0 | 252 | 2 | 0 [09/30/20, 16:41:14:598] error: SCREENS (T359LF935) Could not find matching display for screen 0 with id [09/30/20, 16:41:14:604] error: SCREENS (T359LF935) Could not find matching display for screen 1 with id any help ?

As far as I can tell there is no way to select a single screen to share in the Linux Slack app when you have more than one screen. So in my 3 screen set up, screen sharing is practically unusable. So I was wondering if there was a way to maybe "trick" Slack (or any other Linux app) into thinking I only have one screen through some kind of config file/environment variable etc? I've tried locking Slack to one screen using KDE's "Special Application Settings" functionality, but that didn't do it. Any other suggestions? I'm running Kubuntu 18.04. Thanks!