Slack 3.3.3 crash on Ubuntu 18.10
I have installed the latest Slack 3.3.3 from the official website. Downloaded the deb package, but when i start it, it simply crash and nothing happens. It was working fine on Ubuntu 18.04. Is there a way to debug why this app its not working? Thanks!
Link where i downloaded slack from
When trying to run slack with sudo snap run slack i am getting those errors
mkdir: cannot create directory '/run/user/0': Permission denied
No protocol specified
(spotify:5309): Gtk-WARNING **: cannot open display: :0
and when i run it without sudo my whole system crash and restarts by itself.
UPDATE
I wrote to slack and this is what they have answered me
Thanks for getting in touch, and I'm sorry for the troubles with Slack
on Ubuntu 18.10.
We're aware of the issue, and we're already working on a solution.
We're confident that we'll be able to put out a version update with a
fix very soon. Sorry for the inconvenience here.
deb 18.10 debug slack
asked Oct 25 '18 at 8:33
Dimitar
210111
add a comment |
I have installed the latest Slack 3.3.3 from the official website. Downloaded the deb package, but when i start it, it simply crash and nothing happens. It was working fine on Ubuntu 18.04. Is there a way to debug why this app its not working? Thanks!
Link where i downloaded slack from
When trying to run slack with sudo snap run slack i am getting those errors
mkdir: cannot create directory '/run/user/0': Permission denied
No protocol specified
(spotify:5309): Gtk-WARNING **: cannot open display: :0
and when i run it without sudo my whole system crash and restarts by itself.
UPDATE
I wrote to slack and this is what they have answered me
Thanks for getting in touch, and I'm sorry for the troubles with Slack
on Ubuntu 18.10.
We're aware of the issue, and we're already working on a solution.
We're confident that we'll be able to put out a version update with a
fix very soon. Sorry for the inconvenience here.
deb 18.10 debug slack
asked Oct 25 '18 at 8:33
Dimitar
210111
snap run hellooutputsHello, World!like it suppose to, but slack and spotify dosent work (i havent tried others snaps)
– Dimitar
Oct 26 '18 at 8:56
thanks anyway for your help!
– Dimitar
Oct 26 '18 at 9:56
add a comment |
I have installed the latest Slack 3.3.3 from the official website. Downloaded the deb package, but when i start it, it simply crash and nothing happens. It was working fine on Ubuntu 18.04. Is there a way to debug why this app its not working? Thanks!
Link where i downloaded slack from
When trying to run slack with sudo snap run slack i am getting those errors
mkdir: cannot create directory '/run/user/0': Permission denied
No protocol specified
(spotify:5309): Gtk-WARNING **: cannot open display: :0
and when i run it without sudo my whole system crash and restarts by itself.
UPDATE
I wrote to slack and this is what they have answered me
Thanks for getting in touch, and I'm sorry for the troubles with Slack
on Ubuntu 18.10.
We're aware of the issue, and we're already working on a solution.
We're confident that we'll be able to put out a version update with a
fix very soon. Sorry for the inconvenience here.
deb 18.10 debug slack
asked Oct 25 '18 at 8:33
Dimitar
210111
I have installed the latest Slack 3.3.3 from the official website. Downloaded the deb package, but when i start it, it simply crash and nothing happens. It was working fine on Ubuntu 18.04. Is there a way to debug why this app its not working? Thanks!
Link where i downloaded slack from
When trying to run slack with sudo snap run slack i am getting those errors
mkdir: cannot create directory '/run/user/0': Permission denied
No protocol specified
(spotify:5309): Gtk-WARNING **: cannot open display: :0
and when i run it without sudo my whole system crash and restarts by itself.
UPDATE
I wrote to slack and this is what they have answered me
Thanks for getting in touch, and I'm sorry for the troubles with Slack
on Ubuntu 18.10.
We're aware of the issue, and we're already working on a solution.
We're confident that we'll be able to put out a version update with a
fix very soon. Sorry for the inconvenience here.
deb 18.10 debug slack
deb 18.10 debug slack
asked Oct 25 '18 at 8:33
Dimitar
210111
asked Oct 25 '18 at 8:33
Dimitar
210111
edited Oct 26 '18 at 8:07
asked Oct 25 '18 at 8:33
Dimitar
210111
asked Oct 25 '18 at 8:33
Dimitar
210111
asked Oct 25 '18 at 8:33
Dimitar
210111
210111
snap run hellooutputsHello, World!like it suppose to, but slack and spotify dosent work (i havent tried others snaps)
– Dimitar
Oct 26 '18 at 8:56
thanks anyway for your help!
– Dimitar
Oct 26 '18 at 9:56
add a comment |
snap run hellooutputsHello, World!like it suppose to, but slack and spotify dosent work (i havent tried others snaps)
– Dimitar
Oct 26 '18 at 8:56
thanks anyway for your help!
– Dimitar
Oct 26 '18 at 9:56
snap run hello outputs Hello, World! like it suppose to, but slack and spotify dosent work (i havent tried others snaps)– Dimitar
Oct 26 '18 at 8:56
snap run hello outputs Hello, World! like it suppose to, but slack and spotify dosent work (i havent tried others snaps)– Dimitar
Oct 26 '18 at 8:56
thanks anyway for your help!
– Dimitar
Oct 26 '18 at 9:56
thanks anyway for your help!
– Dimitar
Oct 26 '18 at 9:56
add a comment |
2 Answers
2
active
oldest
votes
Same here after update Ubuntu from 18.04 to 18.10 yesterday.
Slack v3.3.1 stopped working. Tried update to v3.3.3 with no luck.
Both Official Slack deb versions.
Trying run Slack from terminal, 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
answered Oct 31 '18 at 16:02
Diego Bandeira
31127
1
it's a good workaround. it worked for me. so basicly the idea is to take thelibnode.sofile from atom and create symbolic link to slack and use the same file. nice!
– Dimitar
Nov 1 '18 at 8:49
3
If you dont have atom you can still find another suitable library in your sistem with:sudo updatedb && locate libnode. I use the one from VSCode, without installing atom
– mxlian
Nov 1 '18 at 9:19
1
just found on another thread: "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."
– fmi
Nov 13 '18 at 8:48
1
now every time i receive a message in Slack my Slack crash and then restarts which is super annoying so i am waiting for the official fix
– Dimitar
Nov 22 '18 at 7:40
add a comment |
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.
answered Dec 17 '18 at 13:56
Sebastian Tirelli
111
i just tested out with slack 3.1.1 and i can confirm it is working. you can download this version from slackbuilds.org/repository/14.2/network/slack
– Dimitar
Dec 18 '18 at 9:22
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "89"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1087052%2fslack-3-3-3-crash-on-ubuntu-18-10%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
Same here after update Ubuntu from 18.04 to 18.10 yesterday.
Slack v3.3.1 stopped working. Tried update to v3.3.3 with no luck.
Both Official Slack deb versions.
Trying run Slack from terminal, 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
answered Oct 31 '18 at 16:02
Diego Bandeira
31127
1
it's a good workaround. it worked for me. so basicly the idea is to take thelibnode.sofile from atom and create symbolic link to slack and use the same file. nice!
– Dimitar
Nov 1 '18 at 8:49
3
If you dont have atom you can still find another suitable library in your sistem with:sudo updatedb && locate libnode. I use the one from VSCode, without installing atom
– mxlian
Nov 1 '18 at 9:19
1
just found on another thread: "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."
– fmi
Nov 13 '18 at 8:48
1
now every time i receive a message in Slack my Slack crash and then restarts which is super annoying so i am waiting for the official fix
– Dimitar
Nov 22 '18 at 7:40
add a comment |
Same here after update Ubuntu from 18.04 to 18.10 yesterday.
Slack v3.3.1 stopped working. Tried update to v3.3.3 with no luck.
Both Official Slack deb versions.
Trying run Slack from terminal, 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
answered Oct 31 '18 at 16:02
Diego Bandeira
31127
1
it's a good workaround. it worked for me. so basicly the idea is to take thelibnode.sofile from atom and create symbolic link to slack and use the same file. nice!
– Dimitar
Nov 1 '18 at 8:49
3
If you dont have atom you can still find another suitable library in your sistem with:sudo updatedb && locate libnode. I use the one from VSCode, without installing atom
– mxlian
Nov 1 '18 at 9:19
1
just found on another thread: "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."
– fmi
Nov 13 '18 at 8:48
1
now every time i receive a message in Slack my Slack crash and then restarts which is super annoying so i am waiting for the official fix
– Dimitar
Nov 22 '18 at 7:40
add a comment |
Same here after update Ubuntu from 18.04 to 18.10 yesterday.
Slack v3.3.1 stopped working. Tried update to v3.3.3 with no luck.
Both Official Slack deb versions.
Trying run Slack from terminal, 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
answered Oct 31 '18 at 16:02
Diego Bandeira
31127
Same here after update Ubuntu from 18.04 to 18.10 yesterday.
Slack v3.3.1 stopped working. Tried update to v3.3.3 with no luck.
Both Official Slack deb versions.
Trying run Slack from terminal, 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
answered Oct 31 '18 at 16:02
Diego Bandeira
31127
edited Oct 31 '18 at 16:20
answered Oct 31 '18 at 16:02
Diego Bandeira
31127
answered Oct 31 '18 at 16:02
Diego Bandeira
31127
answered Oct 31 '18 at 16:02
Diego Bandeira
31127
31127
1
it's a good workaround. it worked for me. so basicly the idea is to take thelibnode.sofile from atom and create symbolic link to slack and use the same file. nice!
– Dimitar
Nov 1 '18 at 8:49
3
If you dont have atom you can still find another suitable library in your sistem with:sudo updatedb && locate libnode. I use the one from VSCode, without installing atom
– mxlian
Nov 1 '18 at 9:19
1
just found on another thread: "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."
– fmi
Nov 13 '18 at 8:48
1
now every time i receive a message in Slack my Slack crash and then restarts which is super annoying so i am waiting for the official fix
– Dimitar
Nov 22 '18 at 7:40
add a comment |
1
it's a good workaround. it worked for me. so basicly the idea is to take thelibnode.sofile from atom and create symbolic link to slack and use the same file. nice!
– Dimitar
Nov 1 '18 at 8:49
3
If you dont have atom you can still find another suitable library in your sistem with:sudo updatedb && locate libnode. I use the one from VSCode, without installing atom
– mxlian
Nov 1 '18 at 9:19
1
just found on another thread: "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."
– fmi
Nov 13 '18 at 8:48
1
now every time i receive a message in Slack my Slack crash and then restarts which is super annoying so i am waiting for the official fix
– Dimitar
Nov 22 '18 at 7:40
1
1
it's a good workaround. it worked for me. so basicly the idea is to take the
libnode.so file from atom and create symbolic link to slack and use the same file. nice!– Dimitar
Nov 1 '18 at 8:49
it's a good workaround. it worked for me. so basicly the idea is to take the
libnode.so file from atom and create symbolic link to slack and use the same file. nice!– Dimitar
Nov 1 '18 at 8:49
3
3
If you dont have atom you can still find another suitable library in your sistem with:
sudo updatedb && locate libnode. I use the one from VSCode, without installing atom– mxlian
Nov 1 '18 at 9:19
If you dont have atom you can still find another suitable library in your sistem with:
sudo updatedb && locate libnode. I use the one from VSCode, without installing atom– mxlian
Nov 1 '18 at 9:19
1
1
just found on another thread: "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."
– fmi
Nov 13 '18 at 8:48
just found on another thread: "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."
– fmi
Nov 13 '18 at 8:48
1
1
now every time i receive a message in Slack my Slack crash and then restarts which is super annoying so i am waiting for the official fix
– Dimitar
Nov 22 '18 at 7:40
now every time i receive a message in Slack my Slack crash and then restarts which is super annoying so i am waiting for the official fix
– Dimitar
Nov 22 '18 at 7:40
add a comment |
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.
answered Dec 17 '18 at 13:56
Sebastian Tirelli
111
i just tested out with slack 3.1.1 and i can confirm it is working. you can download this version from slackbuilds.org/repository/14.2/network/slack
– Dimitar
Dec 18 '18 at 9:22
add a comment |
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.
answered Dec 17 '18 at 13:56
Sebastian Tirelli
111
i just tested out with slack 3.1.1 and i can confirm it is working. you can download this version from slackbuilds.org/repository/14.2/network/slack
– Dimitar
Dec 18 '18 at 9:22
add a comment |
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.
answered Dec 17 '18 at 13:56
Sebastian Tirelli
111
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.
answered Dec 17 '18 at 13:56
Sebastian Tirelli
111
answered Dec 17 '18 at 13:56
Sebastian Tirelli
111
answered Dec 17 '18 at 13:56
Sebastian Tirelli
111
answered Dec 17 '18 at 13:56
Sebastian Tirelli
111
111
i just tested out with slack 3.1.1 and i can confirm it is working. you can download this version from slackbuilds.org/repository/14.2/network/slack
– Dimitar
Dec 18 '18 at 9:22
add a comment |
i just tested out with slack 3.1.1 and i can confirm it is working. you can download this version from slackbuilds.org/repository/14.2/network/slack
– Dimitar
Dec 18 '18 at 9:22
i just tested out with slack 3.1.1 and i can confirm it is working. you can download this version from slackbuilds.org/repository/14.2/network/slack
– Dimitar
Dec 18 '18 at 9:22
i just tested out with slack 3.1.1 and i can confirm it is working. you can download this version from slackbuilds.org/repository/14.2/network/slack
– Dimitar
Dec 18 '18 at 9:22
add a comment |
Thanks for contributing an answer to Ask Ubuntu!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1087052%2fslack-3-3-3-crash-on-ubuntu-18-10%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
snap run hellooutputsHello, World!like it suppose to, but slack and spotify dosent work (i havent tried others snaps)– Dimitar
Oct 26 '18 at 8:56
thanks anyway for your help!
– Dimitar
Oct 26 '18 at 9:56