Segfault after Ubuntu 17.10 upgrade

[khaeru]

Prerequisites

• Put an X between the brackets on this line if you have done all of the following: [snip]

Description

After an upgrade to Ubuntu 17.10 "artful aardvark", and installing 1.21.1 from the official amd64 .deb, Atom will not start.

Steps to Reproduce

$ atom

Expected behavior: Atom starts.

Actual behavior: /usr/bin/atom: line 129: 9862 Segmentation fault (core dumped) nohup "$ATOM_PATH" --executed-from="$(pwd)" --pid=$$ "$@" > "$ATOM_HOME/nohup.out" 2>&1

Reproduces how often: 100%

Versions

Ubuntu 17.10
https://github.com/atom/atom/releases/tag/v1.21.1

atom --version gives no output.

$ apm --version
apm  1.18.5
npm  3.10.10
node 6.9.5 x64
python 2.7.14
git 2.14.1

[laurentpayot]

Same here after I upgraded from Ubuntu 17.04 to 17.10.

With atom installed via atom.io debian package:

laurent@pinkmoon:~$ atom
laurent@pinkmoon:~$ /usr/bin/atom : ligne 129 : 24411 Erreur de segmentation  (core dumped) nohup "$ATOM_PATH" --executed-from="$(pwd)" --pid=$$ "$@" > "$ATOM_HOME/nohup.out" 2>&1

laurent@pinkmoon:~$ atom --version
laurent@pinkmoon:~$ 

With atom installed via snap:

laurent@pinkmoon:~$ atom
Erreur de segmentation (core dumped)
laurent@pinkmoon:~$ atom --version
Gtk-Message: Failed to load module "overlay-scrollbar"
Gtk-Message: Failed to load module "overlay-scrollbar"
/usr/share/themes/Ambiance/gtk-2.0/apps/mate-panel.rc:30: error: invalid string constant "murrine-scrollbar", expected valid string constant
Atom    : 1.21.1
Electron: 1.6.15
Chrome  : 56.0.2924.87
Node    : 7.4.0
laurent@pinkmoon:~$

[laurentpayot]

And I can not launch atom neither with Gnome nor with Unity.
Interestingly vscode (insiders) is not working either.

This is a major bug, I can't really work anymore 😞 A quick fix/workaround would be really appreciated…

[rsese]

Thanks for the reports - when you started in safe mode, was there any difference at all or did Atom crash right after starting?

I'll try to install 17.10 and test today.

[laurentpayot]

I didn't even know that there was a --safe option. It's quite ugly but it is working in safe mode.

[khaeru]

Thanks, @rsese! I did follow the instruction in the bug template to run atom --safe. Unfortunately (unlike @laurentpayot) I get the same segfault with that option.

[laurentpayot]

Actually, for me, now atom is working in "normal" mode too. I didn't change anything. Weird.
Either the --safe option changed something, or there is a random succession of events at startup that make it start or not.

I'm not touching anything now, I'm too glad it's working 🙄

And thanks @rsese !

[rsese]

Finally had a chance to install 17.10 and then installed Atom 1.21.1. I ran into the error described in #14358, but after running sudo apt --fix-broken install, that fixed things up and Atom started ok.

@khaeru did you also try temporarily resetting to factory defaults?

http://flight-manual.atom.io/hacking-atom/sections/debugging/#reset-to-factory-defaults

[khaeru]

@rsese yes—that was part of the "Prerequisites" in the bug template (along with --safe, as we discussed previously) so did I try that. I had been using a custom location by setting the ATOM_HOME environment variable, so I also unset that. Same symptoms.

[Puller]

Same here...
Really annoying. Reset to Factory settings and Safe mode do not help either!

[laurentpayot]

Are you guys using gnome system-monitor? It displays system informations in gnome shell status bar, such as memory usage, cpu usage, network rate etc. It may interfere with atom title display, because that's the only thing I can remember playing with between my non-working and my working atom.

[Puller]

Hi, I don't use gnome-system-monitor. However, I reinstalled Ubuntu 17.10 from scratch and now it's working with the official Debian package from the Atom website. The snappy package from Ubuntu failed however during installation. Seems to be an Ubuntu problem... Regards, Ben 2017-10-23 10:27 GMT+02:00 Laurent Payot <notifications@github.com>:

…

Are you guys using gnome system-monitor? It displays system informations in gnome shell status bar, such as memory usage, cpu usage, network rate etc. It may interfere with atom title display, because that's the only thing I can remember playing with between my non-working and my working atom. — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#15944 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ADQjrS4hNoQ8_euGRISwRwecjKnRNK1Pks5svE3cgaJpZM4P_1E8> .

[khaeru]

FYI, I have two computers: a laptop and a desktop; the former displays the bug, the latter does not (ie. Atom 1.21.1 works, no segfault, after Ubuntu 17.10 upgrade). I will try to diff a list of installed packages between the two systems, and inspect Atom-related files, sometime today or tomorrow to determine what might be causing this issue.

In any case, it would be lovely if there were also an atom-dbg package that could be installed to produce a human-readable stack trace when things like this happen…

PS. @laurentpayot gnome-system-monitor appears to be installed on both systems, but like @Puller I never use it.