Unable to use atom on Fedora 35

[trinaryouroboros]

Prerequisites

• [x] 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

Fresh install of Atom crashing on startup using Fedora release 35

Steps to Reproduce

1. run atom, or atom --safe

Expected behavior:

Atom should just open

Actual behavior:

Atom startup produces this warning:

expr: syntax error: missing argument after ‘8’

After several seconds it crashes with the following:

/usr/bin/atom: line 195: 175563 Illegal instruction     (core dumped) nohup "$ATOM_PATH" --executed-from="$(pwd)" --pid=$$ "$@" > "$ATOM_HOME/nohup.out" 2>&1
(electron) Sending uncompressed crash reports is deprecated and will be removed in a future version of Electron. Set { compress: true } to opt-in to the new behavior. Crash reports will be uploaded gzipped, which most crash reporting servers support.
(node:175563) electron: The default of contextIsolation is deprecated and will be changing from false to true in a future release of Electron.  See https://github.com/electron/electron/issues/23506 for more information
[175563:1118/145936.535917:FATAL:gpu_data_manager_impl_private.cc(445)] GPU process isn't usable. Goodbye.
--2022-11-18 14:59:36--  https://atom.io/crash_reports
Resolving atom.io (atom.io)... 20.119.16.4
Connecting to atom.io (atom.io)|20.119.16.4|:443... connected.
HTTP request sent, awaiting response... 204 No Content
2022-11-18 14:59:37 (0.00 B/s) - ‘/dev/fd/4’ saved [0]


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


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

Reproduces how often:

100%

Versions

$ atom --version Atom : 1.63.0 Electron: 11.5.0 Chrome : 87.0.4280.141 Node : 12.18.3

$ apm --version apm 2.6.2 npm 6.14.13 node 12.14.1 x64 atom 1.63.0 python 3.10.5 git 2.35.3

Fedora linux release 35

Additional Information

No configuration

I have also attempted the following commands and it still crashes the same:

atom --disable-gpu
atom --in-progress-gpu
atom --no-sandbox

[dsmithhfx]

I've been running atom on Fedora 35 (and Windows, and OS X) for quite some time, mostly without issue. Note my FC35 install is a bit unconventional: server +xfce. Not sure what atom release I've got on FC35 currently, it was working as of last week when I last ran it. Really disappointed to hear it has been EOL'd!

[DeeDeeG]

I believe this is the same problem as https://github.com/atom/atom/issues/23036.

You should be able to launch it with --no-sandbox or --in-process-gpu. There are more details in that issue.