27

I've updated to Ubuntu 18.10 yesterday. Now I can't find a version of Slack which isn't crashing. Tried the version from snap and also the download from the site. Has someone found a working version?

trickreich
  • 473
  • 2
  • 5
  • 9

5 Answers5

14

Looks as if there's problem in the underlying electron app: Every electron based app is affected atm.

So i suggest to wait for an updated slack app and use the web interface in the meanwhile.

fmi
  • 161
  • 4
  • here is more info on it https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1790966 – fmi Oct 21 '18 at 18:20
  • wow.. that's hard. They released a new Ubuntu version on which no electron based app is running. Thanks for your hint! – trickreich Oct 22 '18 at 05:47
  • Talk about not testing your code...I mean they didn't even run it once or they would have seen the blatant segfault – Steampunkery Oct 27 '18 at 05:12
  • 7
    In the meantime there is a solution. The problem is in the outdated version of /usr/lib/slack/libnode.so. You can replace it. One way if you already use VSCode or Atom: `sudo ln -sf /usr/share/code/libnode.so /usr/lib/slack/libnode.so`. For atom just replace `code` with `atom` in the path. – mxlian Nov 01 '18 at 09:15
  • 2
    You can also find other instances of libnode.so in your system with: `sudo updatedb && locate libnode` – mxlian Nov 01 '18 at 09:17
  • 2
    All electron apps are not affected. I have the same issue with slack after the upgrade to 18.10, but I have two others electron based apps working. – Quentin Nov 01 '18 at 19:55
  • @mxlian Could you please upload your libnode.so somewhere ? – expert Nov 14 '18 at 13:36
9

Looks like same issue on question I've answered early.

Slack v3.3.1 stopped working after update Ubuntu from 18.04 to 18.10 yesterday. Tried update to v3.3.3 with no luck. Both Official Slack deb versions.

Tried run Slack from terminal and it just prints Segmentation fault (core dumped). Based on this, Slack came back to work:

sudo mv /usr/lib/slack/libnode.so /usr/lib/slack/libnode.so.bad
sudo ln -s /usr/share/atom/libnode.so /usr/lib/slack/libnode.so
Diego Bandeira
  • 326
  • 3
  • 8
  • 1
    I tried the same workaround with libnode from postman and insomnia installations, but it was not succeed with an other error. Those versions of libnode do not seem to be compatible with slack `/usr/lib/slack/slack: symbol lookup error: /usr/lib/slack/slack: undefined symbol: udata_setCommonData_59`. – Quentin Nov 01 '18 at 20:00
  • Could you please upload your libnode.so somewhere ? – expert Nov 14 '18 at 13:36
  • libnode from skype worked, libnode from discord didn't – Puggan Se Nov 21 '18 at 00:03
  • 1
    This worked as a charm, but using `code` instead of `atom` – greuze Nov 21 '18 at 11:55
  • Of the 12-odd versions of libnode.so on my system, only the one from /snap/skype/60/ libnode.so worked for me... including 2 other skype versions. – Autumn Dec 14 '18 at 21:41
7

I had the same problem. I tried some repositories and the .deb package () without success. So, I uninstalled the application, restart (I suppose is not necessary) and installed slack by snap:

sudo snap install slack --classic

And... the snap installation runs correctly

Rolando Caldas
  • 81
  • 2
0

Basically, glibc 2.28 causes a segfault (Fedora 29 and other latest/beta distros are affected for the most part). It should be fixed in the next release.

In the meantime, switch to slack 3.1.1 or downgrade glibc to 2.27-3.

Sebastian Tirelli
  • 11
  • 1
0

Has the same probleme! Launched slack on terminal and saw that it was already lauch so the app was never initialising storage. All i did was killed the slack process by doing killall slack and after that it all worked fine.

Fergus Bray
  • 1