Atom and atom-nightly crashing on Fedora 35

[sambo57u]

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

Atom core dumps at start

Steps to Reproduce

1. try to start atom from desktop icon or termial directly
2. n/a
3. n/a

Expected behavior:

atom to start

Actual behavior:

core dumps

Reproduces how often:

every time

Versions

Atom : 1.61.0-nightly1 Electron: 9.4.4 Chrome : 83.0.4103.122 Node : 12.14.1

Fedora 35 with daily updates

Additional Information

SAME ERROR WITH ATOM RELEASE VERSION AND NIGHT:Y

$ /usr/bin/atom-nightly: line 195: 11050 Illegal instruction (core dumped) nohup "$ATOM_PATH" --executed-from="$(pwd)" --pid=$$ "$@" > "$ATOM_HOME/nohup.out" 2>&1 [11050:1213/150145.299022:FATAL:gpu_data_manager_impl_private.cc(439)] GPU process isn't usable. Goodbye. (node:11103) Electron: Loading non-context-aware native module in renderer: '/usr/share/atom-nightly/resources/app.asar.unpacked/node_modules/superstring/build/Release/superstring.node'. This is deprecated, see https://github.com/electron/electron/issues/18397. (node:11103) Electron: Loading non-context-aware native module in renderer: '/usr/share/atom-nightly/resources/app.asar.unpacked/node_modules/pathwatcher/build/Release/pathwatcher.node'. This is deprecated, see https://github.com/electron/electron/issues/18397. --2021-12-13 15:01:45-- https://atom.io/crash_reports Resolving atom.io (atom.io)... 18.205.222.128, 54.237.133.81, 54.161.241.46, ... Connecting to atom.io (atom.io)|18.205.222.128|:443... connected. HTTP request sent, awaiting response... 204 No Content 2021-12-13 15:01:46 (0.00 B/s) - ‘/dev/fd/4’ saved [0]

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

[sambo57u]

I just realized that it is not core dumping on my Lenovo laptop with intel HD graphics with the identical packages Fedora 35 installed! Other machines have Nvidia cards.

[icecream17]

I think this might be a duplicate of #23167 Somehow this issue #22872 also says 204 No content but it's in a different os

[ferdnyc]

I think this might be a duplicate of #23167

It definitely is, they're the exact same GPU-based crash.

Somehow this issue #22872 also says 204 No content but it's in a different os

That's harder to say, as they didn't provide the complete output from the crash (I don't think.) The actual error message we're getting on Fedora would have been output right above the first line they quoted in their report. So there's no way to know (unless they provide more details) whether the user omitted the useful line, or if it wasn't there because their crash was caused by something else.

[ferdnyc]

FWIW, this is affecting both Sublime Merge and Atom, for me. (So, obviously I'm getting a ton of coding done lately. :roll_eyes: ) The only difference is, while Sublime Merge merely pops up an annoying dialog box every time I start it, but still runs, Atom is crashing on startup and is therefore completely unusable.

(ETA:) This issue may unfortunately be the final nail in the coffin, for my Atom usage.

I'd already been feeling like its usefulness was starting to fall off (it seems to be hemorrhaging users, most plugins haven't been updated since 2017-2018, a lot of them are starting to come apart at the seams, issues like the Find/Replace panel's crazy behavior when the streams get crossed between find-in-selection and find-all are starting to feel like they're never going to get addressed, etc...), but if I can't even run it then that makes that choice easy.

And really, any editor where I can set up the same Ctrl+[ and Ctrl+] bindings to outdent/indent the selection (because yes, I do write a lot of Python) can work for me.

[J3RN]

Using atom --no-sandbox as mentioned in #23167 caused Atom to no longer crash for me. Actually, booting Atom with that flag once and clicking around seems to have fixed the issue permanently, I can now launch Atom without specifying the --no-sandbox flag.

[Pysis868]

I have been doing that with Discord and GitKraken, but doesn't work for Atom, even with --safe and my own ATOM_HOME too.. https://github.com/atom/atom/issues/23167#issuecomment-999113262

[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.

https://github.com/electron/electron/issues/15760

Read more above to find info about the electron sandbox.

---

https://github.com/atom/atom/issues/23036#issuecomment-1139239233

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