Can't open links as of a week or two ago. Discord works, so this isn't an Electron and/or Wayland issue. My default browser is Firefox, and I have $BROWSER
set to firefox
, and xdg-open
works fine by itself. Every time I click on a link in Slack, a new sh /usr/bin/xdg-open
process is spawned, and they all stay there even after terminating Slack. Any pointers?
Search Criteria
Package Details: slack-desktop 4.41.97-1
Package Actions
Git Clone URL: | https://aur.archlinux.org/slack-desktop.git (read-only, click to copy) |
---|---|
Package Base: | slack-desktop |
Description: | Slack Desktop (Beta) for Linux |
Upstream URL: | https://slack.com/downloads |
Licenses: | custom |
Submitter: | ogarcia |
Maintainer: | ogarcia |
Last Packager: | ogarcia |
Votes: | 604 |
Popularity: | 1.60 |
First Submitted: | 2015-10-19 09:59 (UTC) |
Last Updated: | 2024-11-14 07:14 (UTC) |
Dependencies (7)
- gtk3 (gtk3-no_deadkeys_underlineAUR, gtk3-classicAUR, gtk3-classic-xfceAUR, gtk3-patched-filechooser-icon-viewAUR)
- libsecret
- libxss
- nss (nss-hgAUR)
- xdg-utils (busking-gitAUR, xdg-utils-slockAUR, mimiAUR, mimi-gitAUR, xdg-utils-handlrAUR, openerAUR, xdg-utils-mimeoAUR, mimejs-gitAUR)
- libappindicator-gtk3 (optional) – Systray indicator support
- org.freedesktop.secrets (keepassxc-gitAUR, gnome-keyring-gitAUR, pass-secrets-gitAUR, keepassxc-allow-aur-extension-originAUR, keepassxc-allow-aur-extension-origin-binAUR, pass-secret-service-binAUR, dssdAUR, pass-secret-service-gitAUR, bitw-gitAUR, gnome-keyring, keepassxc, kwallet, kwallet5) (optional) – Keyring password store support
Required by (0)
Sources (2)
Latest Comments
« First ‹ Previous 1 .. 5 6 7 8 9 10 11 12 13 14 15 .. 48 Next › Last »
alecmev commented on 2021-03-31 14:09 (UTC)
jbmorgado commented on 2020-11-30 11:06 (UTC)
Is missing a dependency: libappindicator-gtk3
Without this, it doesn't show the notification indicator in the status bar on Gnome.
yubo56 commented on 2020-11-18 00:19 (UTC) (edited on 2020-11-18 00:27 (UTC) by yubo56)
I figured out the problem with the browser issue, Slack tries to xdg-open but the xdg-mime query (L827 of /usr/bin/xdg-open on my system) returns
/bin/sh: warning: setlocale: LC_ALL: cannot change locale (en-US) brave-browser.desktop
Seems like some dingus at Slack decided to set the locale to "en-US" instead of "en_US" like all our locale.gen's support
The workaround is the same, just set the BROWSER manually, since xdg-open falls back to BROWSER if it can't find the correct *.desktop file to open the file (and it can't because the "warning" in the message above is part of the desktop filename returned, which obviously will fail to parse). xdg-open by default falls back to a few default web browsers if it can't find an app, L928-930 on my system:
BROWSER=www-browser:links2:elinks:links:lynx:w3m
if has_display; then
BROWSER=x-www-browser:firefox:iceweasel:seamonkey:mozilla:epiphany:konqueror:chromium:chromium-browser:google-chrome:$BROWSER
This also explains why everybody saw firefox being used instead of their default browsers, or google-chrome. Not sure why this doesn't affect slack-electron...
alexz commented on 2020-11-17 23:32 (UTC)
Why is it called Beta
? So confusing, really sounds like the nightly-build, where in fact is the latest stable build ... confusing
Tilley commented on 2020-11-17 19:36 (UTC)
Setting the browser environment variable to fix the Firefox link bug didn't work for me. The links still opened in Firefox and caused Firefox to crash for some reason. Uninstalling Firefox made Slack unable to open links at all. So I tried the slack-electron
package thinking that maybe the Slack team just borked their bundled electron build. Sure enough, slack-electron
opens links in google-chrome just like I wanted it to. Hope this helps someone else.
lira commented on 2020-11-13 23:05 (UTC) (edited on 2020-11-13 23:11 (UTC) by lira)
@goddva, thanks for the reply and workaround.
For someone who might need:
vim /usr/share/applications/slack.desktop
[Desktop Entry]
...
Exec=env BROWSER=brave /usr/bin/slack -s %U
....
goddva commented on 2020-11-13 18:23 (UTC)
@victortrac @Thornycrackers @lira - I had the same issue with Slack not using my default browser. A quick look of processing spawning, I do see that it uses xdg-open <URL>
. But all my settings are correct, so it should open in Chrome... but no luck.
However, Slack do use the BROWSER environment variable if its set, so a
BROWSER=google-chrome slack
would be my workaround until it gets fixed, or I do have more time to see what really happens...
crystal_pepsi commented on 2020-11-13 11:04 (UTC) (edited on 2020-11-13 11:11 (UTC) by crystal_pepsi)
After the install, slack doesn't seem to launch at all - I'm not really sure how to proceed here. I tried installing 4.10.3, but that didn't launch on my system either!
EDIT: Deleted my ~/.config/slack then tried again - slack now launches
lira commented on 2020-11-13 00:14 (UTC)
4.11.x broke the default browser for me too. I have the brave as my default and it was opening all the links in firefox. I downgraded to 4.10.3 and everything is working again.
Pinned Comments
ogarcia commented on 2020-02-06 11:44 (UTC) (edited on 2020-02-06 11:44 (UTC) by ogarcia)
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
orpatch
or whatever, please read the wiki.