Why does Slack return a Segmentation fault after Fedora 29 upgrade?

Flat picture Flat · Oct 31, 2018 · Viewed 10.8k times · Source

I have upgraded Fedora from 28 to the latest 29 and Slack doesn't work anymore. It returns a Segmentation fault (core dumped).

Edit: The issue has been fixed on Slack 3.3.4

Answer

Flat picture Flat · Oct 31, 2018

With valgrind I obtained this output:

Process terminating with default action of signal 11 (SIGSEGV): dumping core
 Bad permissions for mapped region at address 0xDBF060
   at 0xDBF060: ??? (in /usr/lib/slack/slack)
   by 0x7112071: node::http2::Http2Session::Callbacks::Callbacks(bool) (in /usr/lib/slack/libnode.so)
   by 0x7112134: ??? (in /usr/lib/slack/libnode.so)
   by 0x5853CE9: call_init.part.0 (in /usr/lib64/ld-2.28.so)
   by 0x5853DE9: _dl_init (in /usr/lib64/ld-2.28.so)
   by 0x5845149: ??? (in /usr/lib64/ld-2.28.so)

It seems the issue is inside an "outdated" version of libnode.so. I just copied another version of libnode.so from the latest atom.rpm installation with:

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


Edit

Like user Pierre Bellan already said, you can easily find other version of libnode.so on your OS with: sudo updatedb && locate libnode

I used the atom one because I was sure about a recent working update of the editor.