Fresh install of atom 1.60.0 crashes on Fedora Linux 35 (Workstation Edition)

[pshanks01]

Prerequisites

• Put an X between the brackets on this line if you have done all of the following:
  • Reproduced the problem in Safe Mode: https://flight-manual.atom.io/hacking-atom/sections/debugging/#using-safe-mode
  • Followed all applicable steps in the debugging guide: https://flight-manual.atom.io/hacking-atom/sections/debugging/
  • Checked the FAQs on the message board for common solutions: https://discuss.atom.io/c/faq
  • Checked that your issue isn't already filed: https://github.com/issues?utf8=✓&q=is%3Aissue+user%3Aatom
  • Checked that there is not already an Atom package that provides the described functionality: https://atom.io/packages

Description

atom launches (empty window appears) and then crashes immediately with the following output to ~/.atom/nohup.out

[222940:0404/145510.496703:FATAL:gpu_data_manager_impl_private.cc(439)] GPU process isn't usable. Goodbye.
--2022-04-04 14:55:10-- https://atom.io/crash_reports
Resolving atom.io (atom.io)... 52.202.168.65, 54.237.133.81, 54.161.241.46, ...
Connecting to atom.io (atom.io)|52.202.168.65|:443... connected.
HTTP request sent, awaiting response... 204 No Content
2022-04-04 14:55:12 (0.00 B/s) - ‘/dev/fd/4’ saved [0]

Unexpected crash report id length
Failed to get crash dump id.
Report Id:
--2022-04-04 14:55:12-- https://atom.io/crash_reports
Resolving atom.io (atom.io)... 52.202.168.65, 54.237.133.81, 54.161.241.46, ...
Connecting to atom.io (atom.io)|52.202.168.65|:443... connected.
HTTP request sent, awaiting response... 204 No Content
2022-04-04 14:55:13 (0.00 B/s) - ‘/dev/fd/4’ saved [0]

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

Steps to Reproduce

1. install atom from RPM file (sudo rpm -i ./atom.x86_64.rpm)
2. atom --version
   Atom : 1.60.0
   Electron: 9.4.4
   Chrome : 83.0.4103.122
   Node : 12.14.1
3. launch atom from command line -- see nohup.out for results

Expected behavior:

atom gui appears and is functional

Actual behavior:

Window appears and disappears again.

Reproduces how often:

100%, consistent

Versions

atom --version
Atom : 1.60.0
Electron: 9.4.4
Chrome : 83.0.4103.122
Node : 12.14.1

Desktop version info:
Fedora Linux 35 (Workstation Edition)
GNOME 41.5
X11 windowing system
Processor: Intel® Core™ i7-8700T CPU @ 2.40GHz × 12
Graphics: NVIDIA Corporation GP107GL [Quadro P620]

Additional Info:
free -h
total used free shared buff/cache available
Mem: 31Gi 7.7Gi 7.5Gi 219Mi 16Gi 22Gi
Swap: 8.0Gi 849Mi 7.2Gi

Additional Information

Tried all troubleshooting steps, and crash behavior is unchanged.

[pshanks01]

$ atom --safe
$ /usr/bin/atom: line 195: 229234 Illegal instruction (core dumped) nohup "$ATOM_PATH" --executed-from="$(pwd)" --pid=$$ "$@" > "$ATOM_HOME/nohup.out" 2>&1
(node:229307) Electron: Loading non-context-aware native module in renderer: '/usr/share/atom/resources/app.asar.unpacked/node_modules/superstring/build/Release/superstring.node'. This is deprecated, see electron/electron#18397.
(node:229307) Electron: Loading non-context-aware native module in renderer: '/usr/share/atom/resources/app.asar.unpacked/node_modules/oniguruma/build/Release/onig_scanner.node'. This is deprecated, see electron/electron#18397.
(node:229307) Electron: Loading non-context-aware native module in renderer: '/usr/share/atom/resources/app.asar.unpacked/node_modules/tree-sitter-c/build/Release/tree_sitter_c_binding.node'. This is deprecated, see electron/electron#18397.
(node:229307) Electron: Loading non-context-aware native module in renderer: '/usr/share/atom/resources/app.asar.unpacked/node_modules/tree-sitter-cpp/build/Release/tree_sitter_cpp_binding.node'. This is deprecated, see electron/electron#18397.
(node:229307) Electron: Loading non-context-aware native module in renderer: '/usr/share/atom/resources/app.asar.unpacked/node_modules/tree-sitter-css/build/Release/tree_sitter_css_binding.node'. This is deprecated, see electron/electron#18397.
(node:229307) Electron: Loading non-context-aware native module in renderer: '/usr/share/atom/resources/app.asar.unpacked/node_modules/tree-sitter-go/build/Release/tree_sitter_go_binding.node'. This is deprecated, see electron/electron#18397.
(node:229307) Electron: Loading non-context-aware native module in renderer: '/usr/share/atom/resources/app.asar.unpacked/node_modules/tree-sitter-embedded-template/build/Release/tree_sitter_embedded_template_binding.node'. This is deprecated, see electron/electron#18397.
(node:229307) Electron: Loading non-context-aware native module in renderer: '/usr/share/atom/resources/app.asar.unpacked/node_modules/tree-sitter-html/build/Release/tree_sitter_html_binding.node'. This is deprecated, see electron/electron#18397.
[229234:0404/152055.668980:FATAL:gpu_data_manager_impl_private.cc(439)] GPU process isn't usable. Goodbye.
--2022-04-04 15:20:55-- https://atom.io/crash_reports
Resolving atom.io (atom.io)... 18.205.222.128, 54.161.241.46, 54.237.133.81, ...
Connecting to atom.io (atom.io)|18.205.222.128|:443... connected.
HTTP request sent, awaiting response... 204 No Content
2022-04-04 15:20:57 (0.00 B/s) - ‘/dev/fd/4’ saved [0]

Unexpected crash report id length
Failed to get crash dump id.
Report Id:
--2022-04-04 15:20:57-- https://atom.io/crash_reports
Resolving atom.io (atom.io)... 18.205.222.128, 54.237.133.81, 52.202.168.65, ...
Connecting to atom.io (atom.io)|18.205.222.128|:443... connected.
HTTP request sent, awaiting response... 204 No Content
2022-04-04 15:20:58 (0.00 B/s) - ‘/dev/fd/4’ saved [0]

[pshanks01]

Further research suggests that this is a problem with Electron or one of its dependencies. But since it affects atom, it may be worth the atom devs chasing it down.
Launching with "atom --in-process-gpu" is a temporary workaround.

[ghost]

Workaround: atom --no-sandbox

Be advised: using --no-sandbox disables the electron sandbox, and could leave you vulnerable to attacks when installing outdated/unverified packages.

electron/electron#15760

Read more above to find info about the electron sandbox.

---

#23036 (comment)

This is a duplicate of #23036 and the issue should be closed. Please follow the link above for more information on this issue.