[Quick Tip] Slack App Not Launching in Ubuntu 18.10

Last updated: November 2, 2018

Slack team communication tool icon

For Ubuntu 18.10, the current Slack desktop 3.3.3 does not launch due to outdated libnode.so library. It outputs Segmentation fault (core dumped) when trying to launch from terminal.

Before the software developer team rebuild or update Slack for Linux, here’s a workaround to make Slack work in Ubuntu 18.10.

Note this is only a workaround for Slack for Linux installed by .DEB package provided via Slack website.

1. Open terminal either via Ctrl+Alt+T keyboard shortcut or from application launcher. When it opens, run command:

sudo updatedb && locate libnode

The command lists all available libnode.so library in your system.

2. In my case (see the previous picture), I have /usr/share/atom-beta/libnode.so other than the one shipped by Slack.

Run command to make a backup of libnode.so privided by Slack:

sudo mv /usr/lib/slack/libnode.so /usr/lib/slack/libnode.so.old

Then replace the library with another one:

sudo ln -s /usr/share/atom-beta/libnode.so /usr/lib/slack/libnode.so

NOTE IN THE LAST COMMAND replace /usr/share/atom-beta/libnode.so depends on the outputs in step 1.

That’s it. Enjoy!

via: stackoverflow.com


I'm a freelance blogger who started using Ubuntu in 2007 and wishes to share my experiences and some useful tips with Ubuntu beginners and lovers. Please comment to let me know if the tutorial is outdated! And, notify me if you find any typo/grammar/language mistakes. English is not my native language. Contact me via [email protected] Buy me a coffee: https://ko-fi.com/ubuntuhandbook1

16 responses to [Quick Tip] Slack App Not Launching in Ubuntu 18.10

  1. Hi! There are several ways to work around the seg fault which occurs on Ubuntu 18.10. This seg fault was first reported by the Arch Linux community (https://github.com/electron/electron/issues/13972 – there’s a lot of discussion here) when glibc was updated from 2.27 to 2.28. Reverting to glibc 2.27 (when possible) resolves the issue. Also using the Slack Snap package is another good alternative.

  2. Thank you. I launch slack on my computer, but slack reloads after every notification

    • I read about a few other people having similar issues with notifications. iirc, it had something to do with their notification daemon.

    • From the PR I mentioned above — For Slack users who replaced libnode.so from somewhere else (and got the app running again) but still get the occasional crash, disable your notification sound for now. It seems if Slack tries to play the notification sound for a new message, it simply restarts instead of ever getting around to playing the clip.

  3. I have the same problem, but I have no other libnode.so on my system. I tried to compile one myself, but then slack complains about an undefined symbol. Where did you get your libnode.so from?

  4. João Pedro Alves November 7, 2018 at 10:22 am

    It worked for me fine. thanks

  5. Michał Przybyłowicz November 14, 2018 at 2:26 pm

    Thanks !

    It work for me with the version of the lib from Code (MS) :

    sudo mv /usr/share/code/libnode.so /usr/lib/slack/libnode.so

  6. Slack has a fix for this in a support build. If you write in to them and tell them you are using glibc 2.28, you can get it.

  7. Adilson dos Santos Dantas December 4, 2018 at 5:16 pm

    I got the same problem with a Debian Sid install.

    It was solved replacing libnode.so with one from Skype. But I got some issues like no notification sound. But it was solved when I replaced libffmpeg.so with one from Skype in the same way that it was done with libnode.so.

    Now slack is fully functional again.

  8. Worked for me, thanks

  9. Thank you, it works!

  10. Worked for me, except I linked to the libnode.so that came with Skype (/usr/share/skypeforlinux/libnode.so). Thanks very much!

  11. Another solution is to uninstall the apt version of slack:

    sudo apt remove slack

    and then re-install it using snap instead:

    sudo snap install slack

    I have no clear idea *why* that works, but it has worked for me on three computers now.

    • It works because snaps use static compilation, so there are no external dependencies on shared libraries.

  12. Thanks, this helped me