afrog icon indicating copy to clipboard operation
afrog copied to clipboard

Latest Atom 1.60 on KUbuntu 22.04 LTS crashed

Open yangbai90 opened this issue 2 years ago • 6 comments

I have tried the atom 1.60 on my newly installed KUbuntu 22.04 LTS, however, it is always crashed. The error message looks like below:

/usr/bin/atom: line 195: 345517 Illegal instruction     (core dumped) nohup "$ATOM_PATH" --executed-from="$(pwd)" --pid=$$ "$@" > "$ATOM_HOME/nohup.out" 2>&1
[345517:0503/145022.183000:FATAL:gpu_data_manager_impl_private.cc(439)] GPU process isn't usable. Goodbye.
(node:345578) 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 https://github.com/electron/electron/issues/18397.
--2022-05-03 14:50:22--  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-05-03 14:50:24 (0,00 B/s) - ‘/dev/fd/4’ saved [0]


Unexpected crash report id length
Failed to get crash dump id.
Report Id: 
--2022-05-03 14:50:24--  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-05-03 14:50:25 (0,00 B/s) - ‘/dev/fd/4’ saved [0]


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

yangbai90 avatar May 03 '22 13:05 yangbai90

I'm experiencing the same exact issue with Ubuntu 22.04. Exact error message. Commenting out lines 171-174 didn't fix my issue either which was causing another issue saying the atom.nemo_action file didn't exist:

171 #Will allow user to get context menu on cinnamon desktop enviroment 172 #if [[ "$(expr substr $(printenv | grep "DESKTOP_SESSION=") 17 8)" == "cinnamon" ]]; then 173 # cp /resources/linux/desktopenviroment/cinnamon/atom.nemo_action /usr/share/nemo/actions/atom.nemo_action 174 #fi

zacwdev avatar May 05 '22 03:05 zacwdev

After reviewing the other issues it looks like adding the -no-sandbox flag was the solution. I created an alias to always add this until the issue is resolved.

alias atom='atom --no-sandbox'

zacwdev avatar May 05 '22 04:05 zacwdev

Hi @zacwdev , thank you so much for the comments, the '--no-sandbox' works perfectly!

yangbai90 avatar May 05 '22 08:05 yangbai90

I can confirm that doing @zacwdev 's solution allows Atom 1.60 to finally work on Ubuntu 22 LTS. Something to note is that previous versions of Atom installable via Snap no longer work on Ubuntu 22 LTS, so this is really the only solution. I'd recommend @darangi add this into the documentation ASAP.

Additionally, the documentation needs to be updated as apt-key has been deprecated:

Key is stored in legacy trusted.gpg keyring (/etc/apt/trusted.gpg), see the DEPRECATION section in apt-key(8) for details.

~ Joe G.

JPGlaser avatar May 17 '22 19:05 JPGlaser

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.

ghost avatar May 27 '22 03:05 ghost

Atom is abandonedware. Due to complications with github being acquired by microsoft, it is unclear if/when this will ever be formally acknowledged. To give an idea of how abandoned this software is:

  • The discussions section was deleted without notice after getting spammed despite methods existing to fix discussion board spam.
  • None of the original maintainers/devs have committed to the repo since 2020
  • There are, as far as I can tell, two official maintainers for this repo these days.
  • The CI pipeline is broken with no indications of being fixed

This software should not be used. Nearly all of its dependencies are ancient, and nobody is left to pass the torch. It is too big, has been touched by too many hands, and has been left to die for too long to be rescued.

If you would like to explore a de-microsfted text editor based on Electron, try VSCodium, a repackaged binary of VSCode's open source codebase with all the microsoft telemetry stripped out, and which uses an open source extension distribution platform separate again from Microsoft.

I personally find it to be quite adequate.

ghost avatar Jun 02 '22 18:06 ghost