1. An image was attached to a post in one of our channels.
2. I hover the mouse over it and click the then-appearing download icon.
3. A "Downloads" side-bar pops up, showing the name of the image file.
4. I hover over the image file name and click the then-appearing "open containing folder" text.
5. Nothing happens.
6. I click the image file name itself
7. Nothing happens.
8. I browse to the "Downloads" folder on my main system, i.e. not inside a flatpak app.
9. The image file is not present in the "Downloads" folder.
10. I also browse "Documents", "Pictures", $HOME and $HOME/.var/app/com.slack.Slack, but the image file is nowhere to be found.

Hi,

I noticed that if I run Slack and then quit the app (File -> Quit) the Slack process remains in the background:

21443 tty2     S+     0:00 bwrap --args 36 slack
21452 tty2     S+     0:00  \_ /app/extra/lib/slack/chrome-sandbox /app/extra/lib/slack/slack --type=zygote

If I do it several times I end up with many background processes. This also happens if I simply hide the window and then run Slack again to bring it to the foreground.

I'm using Slack 4.13.0, flatpak commit f72cdd2c40c9caf6fcf2835efb03c6f6c12836923fd67c7428d201f8dc9edac9, using flatpak 1.2.5 on Debian buster.

The exact same problem is happening with Skype, see flathub/com.skype.Client#135

Steps to reproduce:

• Open slack
• Wait a few seconds

What happens:
Slack screen flashes and an empty "Problem reporting" notification shows up. I'm not sure what causes this, but it seems to keep happening at random intervals. Please note that the main program keeps running, it looks like some secondary process is crashing.

Nov 19 08:46:37 localhost.localdomain com.slack.Slack.desktop[1648]: Creating Slack Application
Nov 19 08:46:37 localhost.localdomain dleyna-renderer-service[7005]: dLeyna: Exit
Nov 19 08:46:47 localhost.localdomain com.slack.Slack.desktop[1648]: [34:1119/084647.302477:FATAL:sync_control_vsync_provider.cc(141)] Calculated bogus refresh interval=495336 us., last_timebase_=1826886650 us., timebase=1827381986 us., last_media_stream_counter_=62, media_stream_counter=63
Nov 19 08:46:47 localhost.localdomain audit[7044]: ANOM_ABEND auid=1000 uid=1000 gid=1000 ses=2 subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 pid=7044 comm="slack" exe="/app/extra/lib/slack/slack" sig=6 res=1
Nov 19 08:46:47 localhost.localdomain systemd[1]: Started Process Core Dump (PID 7148/UID 0).
Nov 19 08:46:47 localhost.localdomain audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=systemd-coredump@9-7148-0 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Nov 19 08:46:47 localhost.localdomain systemd-coredump[7149]: Process 7044 (slack) of user 1000 dumped core.
                                                              
                                                              Stack trace of thread 34:
                                                              #0  0x00007f0e3f69175b n/a (/usr/lib/x86_64-linux-gnu/libc-2.27.so)

After that, you can see this

Nov 19 08:46:48 localhost.localdomain abrt-applet.desktop[2093]: abrt-applet: Can't connect to system DBus: Error calling StartServiceByName for org.freedesktop.problems: GDBus.Error:org.freedesktop.DBus.Error.Spawn.ExecFailed: Failed to execute program org.freedesktop.problems: Permission denied

So the empty "Problem Notification" is probably caused by the lack of permissions

Please update the app to v.3.1.0.

Current linux version is 4.2.0. This version is 4.0.2. Either that, or there's a typo on the flathub site.

On xfce4 icon is a default (fallback gtk) icon, and slack is not in the list of application switcher (alt+tab).
xfce 4.12
opensuse tumbleweed
flatpak 1.2.4

Other flatpaks are working fine, I found this issue only on Slack.

"Leave app running in notification area when the window is closed" option has no effect.

Choosing not to leave the app running will remove the Slack icon (and badges) from your notifications area.

https://get.slack.help/hc/en-us/articles/201355156-Guide-to-Slack-notifications-#linux-1

It works with https://aur.archlinux.org/packages/slack-desktop/

Japanese characters are rendered as boxes within app.
Testing string: 文字化けは嫌いけど、コレはｓｈｉｆｔ−ｊｉｓの問題ではない。

With revision 45cd270cb3a69dc2c9c08cd9211068336fdc52ece08c77e5413a44f70e2a0d5b, I see the same symptoms as in #41: after signing in with the browser, the magic login link opens the Slack app window, but it only shows the Sign In view.

The Window and Status icons are missing. It shows the default fallback icons instead of the Slack icon.

Distro: Manjaro (though I have seen it on others)
DE: KDE Plasma 5.11

Description

On Fedora 33, using the KDE Spin, the Slack flatpak quits after about 30 seconds.

Steps to Reproduce

1. Install Fedora 33 KDE Spin
2. Install com.slack.Slack flatpak --user install com.slack.Slack
3. flatpak run com.slack.Slack

Expected Results

The application should run until I quit it.

Actual Results

It quits after about 30 seconds.

Notes

I have only seen this on the Fedora 33 KDE Spin. I've run the same flatpak on Pop!_OS (so, GNOME on X11), and Fedora 33 Workstation (so, GNOME on Wayland) and it runs fine. I haven't tried another KDE distribution yet.

I get this in my log journal when it quits:

Jan 19 10:21:13 thelio kwin_x11[1762]: qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 1377, resource id: 113246215, major code: 15 (QueryTree), minor code: 0

Hey guys,

Just noticed that the desktop file contains the following parameter:

Exec=/usr/bin/slack --disable-gpu %U

What's the reason for disabling the GPU?

Thanks!

In the flatpak version of the app, in the settings > linux application menu, the first option to launch the app on session start doesn't work. If I select the checkbox, the app shows the "saved" message, but the next time I start my session, the app doesn't launch by default.

Current flatpak app version installed: 3.0.5 64-bit

The current sandbox permissions does not include home, which means that it is impossible to upload files from say ~/workspace. Only specific folders like Documents or Downloads are included in the permissions right now.

Expected: That I can upload a file from ~/workspace.

Actual: Uploading fails with a message about the file type not being supported. If I move the file to ~/Documents and retry, it works without problem.
This is for drag and drop. If you instead try to use the file chooser, you won't be able to see or open all folders, only those currently covered in the filesystem sandbox permissions.

Suggested change:
I suggest that we replace

"--filesystem=xdg-documents:ro",
"--filesystem=xdg-pictures:ro",
"--filesystem=xdg-music:ro",
"--filesystem=xdg-videos:ro",

with

"--filesystem=home:ro",

or simply add it to the current list.

Distro Manjaro Linux 18.02 (up to date)
Kernel: Linux vitor 4.19.13-1-MANJARO #1 SMP PREEMPT Sat Dec 29 15:43:56 UTC 2018 x86_64 GNU/Linux
Slack Version: Direct Download 3.3.7 64-bit

Channel details are missing icons and labels:

Clicking on user name/photo doesn't show their profile info.

I'm not sure if this is a thing I can configure locally, but I'm new to flatpak and haven't figured it out yet if so.

When I join slack calls, I can use my microphone, but the video icon is greyed out and the camera configuration pulldown says "no cameras found". I suspect the build needs something like --device=all (see this section of the manual).

Some time ago Slack on my Manjaro install started to open up URLs on Chromium, instead of my default browser - Brave (xdg-settings get default-web-browser gives me brave-browser.desktop).

When i run flatpak run --command=bash com.slack.Slack and try xdg-open it opens Brave correctly.

Also, the version on Snap opens links correctly.

After I removed Chromium from my system the links stopped opening at all. The other browsers on my system is Firefox.

Can this be an issue of how this app is packaged, or is it a problem with something like https://github.com/flatpak/xdg-desktop-portal?

https://slackhq.com/say-hello-new-logo

Is it somehow possible to make flatpacked Slack open links when clicking on them, or does this need to be fixed upstream?

According to logs "processed" by someone from Slack the problem is with resolving domains like app.slack.com.
Slack works when used via browser, slack-desktop (btw I use Arch ;) from AUR works.

I don't have firewall other than default from docker without containers.

I tried installing with flatpak in (?) user or system - same result.

I'm using systemd-resolvd and my /etc/resolv.conf is empty. After placing there some nameserver slack loads. It's not permanent solution as systemd or NetworkManager are going to replace the file.

Currently, Slack is dumping a lot of log messages to my system log. It appears that the log level is set to info. Would you consider setting it to, for example, warn so that important information is still displayed, while avoiding the flood of messages? If additional information is needed for debugging, there appears to be a way to modify the log level from command line.

flatpak install -v -y com.slack.Slack
F: No installations directory in /etc/flatpak/installations.d. Skipping
F: Opening system flatpak installation at path /var/lib/flatpak
F: Opening user flatpak installation at path /home/jeterokeeffe/.local/share/flatpak
Looking for matches…
F: Fetching summary file for remote ‘flathub’
F: Fetching summary file for remote ‘flathub’
F: Transaction: install flathub:app/com.slack.Slack/x86_64/stable[]
F: Updating remote metadata for flathub
F: marking op install:app/com.slack.Slack/x86_64/stable resolved to 804b4ac18190c41df1f4faebd37e5f35ac472a76e713e7674a198ee0d2a043fe
F: Updating dependent runtime runtime/org.freedesktop.Platform/x86_64/18.08
F: Transaction: update flathub:runtime/org.freedesktop.Platform/x86_64/18.08[$old]
F: marking op update:runtime/org.freedesktop.Platform/x86_64/18.08 resolved to 30d1e0e6f128912bc3e7075e7d55363e9ade59a72c0eac1c21cae237593a7aba
F: Transaction: install/update flathub:runtime/org.freedesktop.Platform.Locale/x86_64/18.08[/en]
F: Transaction: install/update flathub:runtime/org.freedesktop.Platform.html5-codecs/x86_64/18.08[]
F: marking op install/update:runtime/org.freedesktop.Platform.html5-codecs/x86_64/18.08 resolved to 337041240b18dbd4fc70cfd84d45f0f8145d72bdda277639f45beadc52ec6afd
F: marking op install/update:runtime/org.freedesktop.Platform.Locale/x86_64/18.08 resolved to 3756db4fedc7e9f0cf629d978425369e90287fd82570915f1b969c0a7b7dc0e0

com.slack.Slack permissions:
ipc network pulseaudio x11
devices file access [1] dbus access [2]

[1] home, xdg-run/dconf, ~/.config/dconf:ro
[2] ca.desrt.dconf, org.freedesktop.Notifications, org.kde.StatusNotifierWatcher

1. com.slack.Slack	x86_64	stable	flathub	< 57.8 MB
   

Installing… █▌ 8% 53.1 kB/sF: Loading https://downloads.slack-edge.com/linux_releases/slack-desktop-3.3.7-amd64.deb using libsoup
Error: While downloading https://downloads.slack-edge.com/linux_releases/slack-desktop-3.3.7-amd64.deb: Unacceptable TLS certificate
error: Failed to install com.slack.Slack: While downloading https://downloads.slack-edge.com/linux_releases/slack-desktop-3.3.7-amd64.deb: Unacceptable TLS certificate

curl -v https://downloads.slack-edge.com/linux_releases/slack-desktop-3.3.7-amd64.deb

• Trying 146.112.61.106...
• TCP_NODELAY set
• Connected to downloads.slack-edge.com (146.112.61.106) port 443 (#0)
• ALPN, offering h2
• ALPN, offering http/1.1
• successfully set certificate verify locations:
• CAfile: /etc/pki/tls/certs/ca-bundle.crt
  CApath: none
• TLSv1.3 (OUT), TLS handshake, Client hello (1):
• TLSv1.3 (IN), TLS handshake, Server hello (2):
• TLSv1.2 (IN), TLS handshake, Certificate (11):
• TLSv1.2 (OUT), TLS alert, unknown CA (560):
• SSL certificate problem: unable to get local issuer certificate
• Closing connection 0
  curl: (60) SSL certificate problem: unable to get local issuer certificate
  More details here: https://curl.haxx.se/docs/sslcerts.html

curl failed to verify the legitimacy of the server and therefore could not
establish a secure connection to it. To learn more about this situation and
how to fix it, please visit the web page mentioned above.

I'm not sure if this is the right place to report this, but I've been experiencing some GNOME-shell crashes (that is: the whole desktop crashes, not just Slack) that appear to be related to usage of this flatpak. I'm unsure why this happens, but some interactions in Slack will just crash the whole desktop.
I've observed this happen now under both X.org and Wayland display servers.

Details follow:

Operating system:

NAME=Fedora
VERSION="34 (Workstation Edition)"
ID=fedora
VERSION_ID=34
VERSION_CODENAME=""
PLATFORM_ID="platform:f34"
PRETTY_NAME="Fedora 34 (Workstation Edition)"
ANSI_COLOR="0;38;2;60;110;180"
LOGO=fedora-logo-icon
CPE_NAME="cpe:/o:fedoraproject:fedora:34"
HOME_URL="https://fedoraproject.org/"
DOCUMENTATION_URL="https://docs.fedoraproject.org/en-US/fedora/34/system-administrators-guide/"
SUPPORT_URL="https://fedoraproject.org/wiki/Communicating_and_getting_help"
BUG_REPORT_URL="https://bugzilla.redhat.com/"
REDHAT_BUGZILLA_PRODUCT="Fedora"
REDHAT_BUGZILLA_PRODUCT_VERSION=34
REDHAT_SUPPORT_PRODUCT="Fedora"
REDHAT_SUPPORT_PRODUCT_VERSION=34
PRIVACY_POLICY_URL="https://fedoraproject.org/wiki/Legal:PrivacyPolicy"
VARIANT="Workstation Edition"
VARIANT_ID=workstation

Flatpak version:
Flatpak 1.10.2

Slack version:

$ flatpak info com.slack.Slack                                                                                                                                                                                                              

Slack - Chat with your team

          ID: com.slack.Slack
         Ref: app/com.slack.Slack/x86_64/stable
        Arch: x86_64
      Branch: stable
     Version: 4.14.0
     License: LicenseRef-proprietary
      Origin: flathub
  Collection: org.flathub.Stable
Installation: system
   Installed: 5.3 MB
     Runtime: org.freedesktop.Platform/x86_64/20.08
         Sdk: org.freedesktop.Sdk/x86_64/20.08

      Commit: f738078bef50d00d548abcaa88d6432dada3999582bc66b96e36154a6b62420a
      Parent: dfb8851acb9d73bf245ef0260d878fc09c65c9f96703f53ef4cf9d16e55d308c
     Subject: Update slack.deb to 4.14.0 (e0251447)
        Date: 2021-03-20 08:44:53 +0000

Crash log from journalctl:

See attached. This is the most recently observed crash under X.org, which happened shortly after launching Slack. gnome40-shell-crash.txt

This line is highly suspect:

Apr 28 09:13:24 aipom gnome-shell[24124]: Object 0x55e99ae102a0 (a ClutterInputDevice) resurfaced after the JS wrapper was finalized. This is some library doing dubious memory management inside dispose()

If this is the wrong place to report this, I apologize. If I can provide any more useful information, please let me know.

Problem:
Cannot sign in to Slack because the browser sign-in redirect does not work.

Steps to Reproduce:

1. Install com.slack.Slack from Flathub
2. Launch application and click "Sign In"
3. Sign in through web browser
4. Click "Open with xdg-open" when prompted by browser
5. Slack app opens, but the screen is still stuck on the original "Sign In" screen
6. I can click "Sign In" again, and it re-opens the browser etc...

Workaround:
Downgrade to commit 810ae703189dd439c5a7059accf33af495d415e2d46545a3bfcccf445ab7c092

System:
OS: Arch Linux x86_64
Host: 20FDCTO1WW ThinkPad Yoga 260
Kernel: 5.1.6-arch1-1-ARCH
DE: Xfce
WM: Xfwm4
Browser: Chrome or Firefox (same problem)

Hi, I'm using Flatpak Slack on XFCE desktop. Even though I changed the theme to dark, the menubar and the menu (upon right click) remain in white theme.

How can I resolve this, please?

System:

            .-/+oossssoo+/-.               jovial@xpsl502x 
        `:+ssssssssssssssssss+:`           --------------- 
      -+ssssssssssssssssssyyssss+-         OS: Ubuntu 20.04.2 LTS x86_64 
    .ossssssssssssssssssdMMMNysssso.       Host: Dell System XPS L502X 
   /ssssssssssshdmmNNmmyNMMMMhssssss/      Kernel: 5.4.0-65-lowlatency 
  +ssssssssshmydMMMMMMMNddddyssssssss+     Uptime: 3 hours, 27 mins 
 /sssssssshNMMMyhhyyyyhmNMMMNhssssssss/    Packages: 3274 (dpkg), 10 (flatpak), 3 (snap) 
.ssssssssdMMMNhsssssssssshNMMMdssssssss.   Shell: bash 5.0.17 
+sssshhhyNMMNyssssssssssssyNMMMysssssss+   Resolution: 1366x768 
ossyNMMMNyMMhsssssssssssssshmmmhssssssso   DE: Xfce 
ossyNMMMNyMMhsssssssssssssshmmmhssssssso   WM: Xfwm4 
+sssshhhyNMMNyssssssssssssyNMMMysssssss+   WM Theme: Nordic-darker 
.ssssssssdMMMNhsssssssssshNMMMdssssssss.   Theme: Nordic-darker [GTK2], Materia [GTK3] 
 /sssssssshNMMMyhhyyyyhdNMMMNhssssssss/    Icons: Papirus-Dark [GTK2], ubuntustudio [GTK3] 
  +sssssssssdmydMMMMMMMMddddyssssssss+     Terminal: xfce4-terminal 
   /ssssssssssshdmNNNNmyNMMMMhssssss/      Terminal Font: Fira Code 9 
    .ossssssssssssssssssdMMMNysssso.       CPU: Intel i5-2410M (4) @ 2.900GHz 
      -+sssssssssssssssssyyyssss+-         GPU: NVIDIA GeForce GT 525M 
        `:+ssssssssssssssssss+:`           GPU: Intel 2nd Generation Core Processor Family 
            .-/+oossssoo+/-.               Memory: 2721MiB / 11874MiB

If you run Wayland on a HiDPI display and enable display scaling in GNOME (3.36 at the time of this writing), either full or fractional, the Slack window doesn't render fonts accordingly. Supposedly this can be set as per the Arch wiki but I've not been able to make it function as documented in that wiki if I make the suggested edits to /home/admiller/.local/share/flatpak/app/com.slack.Slack/x86_64/stable/03ed7b6d823f379e26c7c0251ed0f61bfc22eaebf395128f658949bdbedb7d5b/files/extra/share/applications/slack.desktop.

Starting with 3.4.2, when I'm in a call with someone, clicking in the call window would make my screen turn mostly black:

This might be a problem with my EXWM window manager but this works fine in 3.4.0. More precisely,

$ sudo flatpak --verbose update --commit=014b6644d7f75120a47e7edce86a875c81b4e27a1844bfcfafcfe6280bdfafd6 com.slack.Slack

does not work whereas

$ sudo flatpak --verbose update --commit=810ae703189dd439c5a7059accf33af495d415e2d46545a3bfcccf445ab7c092 com.slack.Slack

does work.

KO  Commit: 014b6644d7f75120a47e7edce86a875c81b4e27a1844bfcfafcfe6280bdfafd6
   Subject: Update to 3.4.2 (3a013998)
      Date: 2019-06-02 07:17:13 +0000

OK  Commit: 810ae703189dd439c5a7059accf33af495d415e2d46545a3bfcccf445ab7c092
   Subject: Update to 3.4.0 (394c89bb)
      Date: 2019-05-08 07:42:39 +0000

I don't have pulseaudio running (I don't use gnome, and I need realtime audio for using pro audio apps), instead using alsa directly. With this configuration I cannot hear anything and my mic doesn't work.

I don't think it's a problem with slack per se, because I also have a standalone installation (via the Arch User Repo) which works fine with alsa alone.

Is there something I can configure to allow slack access to alsa devices?

Also, I think this would be a useful FAQ, even if it's just to say the flatpak Slack package requires pulseaudio - knowing that in advance would have saved me a bunch of time :)

It seems that running after running Slack in the background for some minutes it will just crash.

Where can I get log files to diagnose this issue? There seem to be some files on ~/.var/app/com.slack.Slack/config/Slack/logs but I'm not sure where to look.

When running it on the terminal it prints this:

[2 preload-host-spawn-strategy] Running: /app/bin/zypak-helper child - /app/extra/lib/slack/slack --type=zygote
Initializing local storage instance
(node:2) [DEP0005] DeprecationWarning: Buffer() is deprecated due to security and usability issues. Please use the Buffer.alloc(), Buffer.allocUnsafe(), or Buffer.from() methods instead.
Gtk-Message: 18:10:47.727: Failed to load module "appmenu-gtk-module"
Gtk-Message: 18:10:47.770: Failed to load module "canberra-gtk-module"
Gtk-Message: 18:10:47.770: Failed to load module "canberra-gtk-module"
(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.
(electron) 'BrowserWindow.getDevToolsExtensions' is deprecated and will be removed. Please use 'session.getAllExtensions' instead.

It doesn't print anything during the crash, but from the log it can be known that it sent an uncompressed crash report after reopening because it had crashed.

After installing Slack from Flat Hub and running com.slack.Slack I am presented with a sign in screen.

On this screen there is a "Sign In" button.

When I click this button, nothing happens.

Clicking the "getting started" link also does not do anything.

From the release notes I think a link is supposed to open in my browser.

% uname -a
Linux apollo 5.0.5_1 #1 SMP PREEMPT Wed Mar 27 18:26:19 UTC 2019 x86_64 GNU/Linux

% lsb_release -a
LSB Version:	1.0
Distributor ID:	VoidLinux
Description:	Void Linux
Release:	rolling
Codename:	void

% flatpak list
Slack - Chat with your team	com.slack.Slack	3.3.8	stable	x86_64	slack-origin	system
Freedesktop.org Application Platform version 18.08 - Shared libraries provided by freedesktop.org	org.freedesktop.Platform		18.08	x86_64	flathub	system
Intel	org.freedesktop.Platform.VAAPI.Intel		18.08	x86_64	flathub	system
html5-codecs	org.freedesktop.Platform.html5-codecs		18.08	x86_64	flathub	system

% flatpak run com.slack.Slack
(electron) 'app.makeSingleInstance(cb)' is deprecated. Use 'app.requestSingleInstanceLock() and app.on('second-instance', cb)' instead.
Creating Slack Application

(slack:2): libappindicator-WARNING **: 03:47:23.223: Unable to get the session bus: Unknown or unsupported transport “disabled” for address “disabled:”

(slack:2): LIBDBUSMENU-GLIB-WARNING **: 03:47:23.223: Unable to get session bus: Unknown or unsupported
transport “disabled” for address “disabled:”

(slack:2): IBUS-WARNING **: 03:47:24.443: Unable to connect to ibus: Unknown or unsupported transport “disabled” for address “disabled:”

Hey guys,

Really great having this flatpak! :-)

But not having an image preview in the open file dialog is kind of a bumper.

Can we somehow enable that?

Thanks!

Robert

As of the last few days, when I run the Flatpak-installed Slack app, my messages are timestamped with the wrong timezone.

The timestamps seem to be UTC. My actual timezone is Brisbane/Australia (UTC+10). So for example, a message received at 1:23pm local time will be shown timestamped 03:23 instead of 13:23.

This doesn't happen if I login to the same Slack workspace through a web browser (e.g. Firefox). In Firefox the correct timestamps (local time) are shown.

I'm running Fedora release 30. I upgraded from Fedora release 29 a few weeks ago. This issue is more recent than that (the last few days).

$ timedatectl
              Local time: Tue 2019-06-04 13:26:01 AEST
          Universal time: Tue 2019-06-04 03:26:01 UTC
                RTC time: Tue 2019-06-04 13:26:01
               Time zone: Australia/Brisbane (AEST, +1000)

$ flatpak run com.slack.Slack
Gtk-Message: 13:20:05.439: Failed to load module "canberra-gtk-module"
Gtk-Message: 13:20:05.439: Failed to load module "pk-gtk-module"
Gtk-Message: 13:20:05.439: Failed to load module "canberra-gtk-module"
Gtk-Message: 13:20:05.439: Failed to load module "pk-gtk-module"
Creating Slack Application

I mention Fedora because the issue doesn't seem to happen on Ubuntu on my laptop, only Fedora on my Desktop. The freezes don't seem to happen as a trigger to something happening (like a message arriving or a notification) and they can persist for a long while. I've basically switched from the flatpak to just visiting the site in Chrome.

espadav8@localhost:~
> flatpak -v --version
Flatpak 0.99.3

espadav8@localhost:~
> flatpak info com.slack.Slack
Ref: app/com.slack.Slack/x86_64/stable
ID: com.slack.Slack
Arch: x86_64
Branch: stable
Origin: flathub
Collection ID: org.flathub.Stable
Date: 2018-08-18 00:17:59 +0000
Subject: Switch to stable runtime version 18.08 (57451b64)
Commit: f1549d47f7d6eb3e7947b5e7b47ba82623c2d342237ab3905708ad80dc4e144e
Parent: efaa01777c1a7f03ce7f9c6b395ae410f19eec8098e59df2787c75eef0712768
Location: /var/lib/flatpak/app/com.slack.Slack/x86_64/stable/f1549d47f7d6eb3e7947b5e7b47ba82623c2d342237ab3905708ad80dc4e144e
Installed size: 2.8 MB
Runtime: org.freedesktop.Platform/x86_64/18.08
Sdk: org.freedesktop.Sdk/x86_64/18.08

Currently, after installing Slack from flathub, it's not being shown in the Cinnamon's menu, due to the lack of a .desktop file being installed.

Spotify (from flathub as well) already shows the right icon.

OS info:

OS: Fedora release 30 (Thirty) x86_64 
Kernel: 5.1.20-300.fc30.x86_64
DE: GNOME 3.32.2 
Theme: Adwaita-dark [GTK2/3] 
Flatpak: 1.4.2

Slack info:

ID: com.slack.Slack
Ref: app/com.slack.Slack/x86_64/stable
Arch: x86_64
Branch: stable
Version: 4.0.1
License: LicenseRef-proprietary
Origin: flathub
Collection: org.flathub.Stable
Installation: system
Installed: 2.8 MB
Runtime: org.freedesktop.Platform/x86_64/18.08
Sdk: org.freedesktop.Sdk/x86_64/18.08
Commit: a10574ca28995af9d14a2510e369e458d47b0b35b78e80b7fae29995b607bd16
Parent: dd864e4fc3d1eab1c29930e1f913bbc83c88cfdaa805a09e088b495563977703
Subject: Update to 4.0.1 (bc4873db)
Date: 2019-07-31 11:43:20 +0000

I signed in into 4 different workspaces, but none is shown when I click on the tray icon. Left or right click, doesn't matter.

Any idea?

Since 4.1.1, Slack no longer starts.

[2:1009/150246.006545:FATAL:setuid_sandbox_host.cc(157)] The SUID sandbox helper binary was found, but is not configured correctly. Rather than run without sandboxing I'm aborting now. You need to make sure that /app/extra/lib/slack/chrome-sandbox is owned by root and has mode 4755.

There is another thread that mentions freezes. I was interested in figuring out how I can find out what the issue is.
I am on fedora 32, and I am getting video freezes when I am in a conference that makes slack totally unresponsive. It seems to happen randomly, all of a sudden the entire video conference window freezes and also the other slack windows are unresponsive. I can still talk and hear others but my webcam is frozen to others.

How can I help figure out what the error is that causes the crash? Where are the logs?

Hi

I'm running the Slack app from Flathub on Fedora 33, and when I use Xorg then I can share my screen during a Slack call. Unfortunately this doesn't work when running Wayland.

Way to reproduce

• Start the Slack app on any Linux box running wayland.
• Start a Slack call with someone.
• Press the "Share my screen" button.

Result
I'm unable to share my desktop screen

Expected result
I expect screen sharing to work, same as it does under Xorg

I know in Chromium, it can easily be activated using Pipewire, by enabling the chrome://flags/#enable-webrtc-pipewire-capturer flag. Not sure if something similar can be done in Electron though.

Thanks for looking in to this!

Nothing happens if I left click on a link, nor if I right click and select "Open link".
This goes for both links directly in a message, to a channel or in DMs, and in embed cards from links.

Slack version: 4.12.2 64-bit dd5cf43-s@1610601554
Running on Fedora 33 with Gnome 3.38.2.
Default browser: Firefox 84.
I installed slack through the "Software" program in Fedora.

The snap version works fine, and reports the exact same slack version (including commit hash).

I'd like to try my hand at providing a pull request to fix this. Is there any documentation for updating a flatpak through this repo?

I'm seeing a similar problem to #43 except my timestamps were correct until the recent Daylight Savings Time change observed in Sydney Australia.

$ timedatectl
               Local time: Thu 2020-10-08 13:34:27 AEDT  
           Universal time: Thu 2020-10-08 02:34:27 UTC   
                 RTC time: Thu 2020-10-08 02:34:27       
                Time zone: Australia/Sydney (AEDT, +1100)
System clock synchronized: yes                           
              NTP service: active                        
          RTC in local TZ: no     

Using this workaround fixed the issue for me: #43 (comment)

As an aside I noticed that changing the Time zone in Preferences had no impact to the timestamps shown on messages.

When using fractional scaling on my external display plugged into my laptop in GNOME 3.36.x on Fedora Workstation 32, if I use Slack from the Flatpak the fonts are very blurry but if I use it on the internal display of the laptop then the fonts are crisp. Please advise.

Release notes: https://slack.com/intl/en-gb/release-notes/linux

Slack Version: 4.0.2
Flatpak Version: 1.2.3
OS: openSUSE Leap 15.1

> flatpak run com.slack.Slack
Initializing local storage instance
(node:2) [DEP0005] DeprecationWarning: Buffer() is deprecated due to security and usability issues. Please use the Buffer.alloc(), Buffer.allocUnsafe(), or Buffer.from() methods instead.
(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.
(electron) 'BrowserWindow.getDevToolsExtensions' is deprecated and will be removed. Please use 'session.getAllExtensions' instead.

(slack:2): libappindicator-WARNING **: 16:02:50.550: Unable to get the session bus: Unknown or unsupported transport “disabled” for address “disabled:”

(slack:2): LIBDBUSMENU-GLIB-WARNING **: 16:02:50.550: Unable to get session bus: Unknown or unsupported transport “disabled” for address “disabled:”
Can't find bus: Unknown or unsupported transport “disabled” for address “disabled:”
Can't find bus: Unknown or unsupported transport “disabled” for address “disabled:”

I don't see any fatal errors, but nevertheless I never see the Slack window appear...

This is happening on Alpine Linux, but I'm unsure what the host OS would have to do with it.

Using Dash to Panel and TopIconsFix

summary says it all. ibus can't activate on slack app at all. even if setting GTK_IM_MODULE=ibus explicitly, slack app seems not communicating to ibus through DBus.

In locked screen the notifications from Slack shows up as Electron with a generic light-blob icon, instead of the Slack's own icon.

OS: openSUSE Tumbleweed
Flatpak version: 1.6.1

flatpak info com.slack.Slack

Slack - Chat with your team

        ID: com.slack.Slack
       Ref: app/com.slack.Slack/x86_64/beta
Arsitektur: x86_64
    Cabang: beta
     Versi: 4.3.2
   Lisensi: LicenseRef-proprietary
      Asal: flathub-beta
   Koleksi: org.flathub.Beta
Pemasangan: system
 Terpasang: 3,0 MB
   Runtime: org.freedesktop.Platform/x86_64/19.08
       Sdk: org.freedesktop.Sdk/x86_64/19.08

     Komit: b729c0b8a4c33f3b728f2f63bbf0872361ac7851c5f228b6c19dac9b0a3b60e8
     Induk: 647c2d5c645bd561127a5203586452ea109f95cdac1ae8c2c750d9985bb2b62a
    Subjek: Update to 4.3.2 (ad235114)
   Tanggal: 2020-02-05 06:12:37 +0000

Already run flatpak run --filesystem=home com.slack.Slack and sudo flatpak override --filesystem=home com.slack.Slack (as described on README.md), but still can't access files and other folders on $HOME