Atom crashes on start - only works with --no-sandbox

I recently installed Manjaro with KDE, and I wanted to give Atom a spin. It refuses to launch through the run dialog at all, and when launched through a terminal with the “atom” command, it flashes the app and crashes with this text:

/usr/bin/atom: line 86:  1478 Illegal instruction     (core dumped) nohup "$ATOM_PATH" --executed-from="$(pwd)" --pid=$$ "$@" > "$ATOM_HOME/nohup.out" 2>&1
[1478:0310/022653.575301:FATAL:gpu_data_manager_impl_private.cc(439)] GPU process isn't usable. Goodbye.
(node:1532) Electron: Loading non-context-aware native module in renderer: '/usr/lib/atom/node_modules/pathwatcher/build/Release/pathwatcher.node'. This is deprecated, see https://github.com/electron/elec
tron/issues/18397.
(node:1532) Electron: Loading non-context-aware native module in renderer: '/usr/lib/atom/node_modules/oniguruma/build/Release/onig_scanner.node'. This is deprecated, see https://github.com/electron/elect
ron/issues/18397.
(node:1532) Electron: Loading non-context-aware native module in renderer: '/usr/lib/atom/node_modules/superstring/build/Release/superstring.node'. This is deprecated, see https://github.com/electron/elec
tron/issues/18397.
(node:1532) Electron: Loading non-context-aware native module in renderer: '/usr/lib/atom/node_modules/tree-sitter/build/Release/tree_sitter_runtime_binding.node'. This is deprecated, see https://github.c
om/electron/electron/issues/18397.
(node:1532) Electron: Loading non-context-aware native module in renderer: '/usr/lib/atom/node_modules/@atom/nsfw/build/Release/nsfw.node'. This is deprecated, see https://github.com/electron/electron/iss
ues/18397.
(node:1532) Electron: Loading non-context-aware native module in renderer: '/usr/lib/atom/node_modules/git-utils/build/Release/git.node'. This is deprecated, see https://github.com/electron/electron/issue
s/18397.
--2022-03-10 02:26:53--  https://atom.io/crash_reports
SSL_INIT
Loaded CA certificate '/etc/ssl/certs/ca-certificates.crt'
Resolving atom.io (atom.io)... 52.202.168.65, 54.161.241.46, 54.237.133.81, ...
Connecting to atom.io (atom.io)|52.202.168.65|:443... connected.
HTTP request sent, awaiting response... 204 No Content
2022-03-10 02:26:55 (0,00 B/s) - ‘/dev/fd/4’ saved [0]

Unexpected crash report id length
Failed to get crash dump id.
Report Id:
--2022-03-10 02:26:55--  https://atom.io/crash_reports
SSL_INIT
Loaded CA certificate '/etc/ssl/certs/ca-certificates.crt'
Resolving atom.io (atom.io)... 52.202.168.65, 54.161.241.46, 54.237.133.81, ...
Connecting to atom.io (atom.io)|52.202.168.65|:443... connected.
HTTP request sent, awaiting response... 204 No Content
2022-03-10 02:26:56 (0,00 B/s) - ‘/dev/fd/4’ saved [0]

Unexpected crash report id length
Failed to get crash dump id.
Report Id:

The only way to start the program is through the terminal with the command “atom --no-sandbox”, which I only found out by googling. I don’t really know what solutions there are, other than to maybe add --no-sandbox to the run dialog options. Which I’d rather avoid.

It’s a known issue, see FS#73957 - [atom] Crashes with Illegal instruction, even in --safe. Why Atom still uses Electron 9 is beyond me.

While insecure, it’s the only workaround that exists.

1 Like

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.