FS#73957 - [atom] Crashes with Illegal instruction, even in --safe

Attached to Project: Community Packages
Opened by Octavia Togami (octylFractal) - Friday, 25 February 2022, 19:27 GMT
Last edited by Caleb Maclennan (alerque) - Thursday, 07 April 2022, 14:15 GMT
Task Type Bug Report
Category Packages
Status Closed
Assigned To Caleb Maclennan (alerque)
Nicola Squartini (tensor5)
Architecture All
Severity High
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 1
Private No

Details

Description: Atom crashes upon launch, even if launched with --safe.


Additional info:
* local/atom 1.58.0-1
* uname -a: Linux Draconnet 5.16.11-zen1-1-zen #1 ZEN SMP PREEMPT Thu, 24 Feb 2022 02:18:22 +0000 x86_64 GNU/Linux
* log from terminal: https://gist.github.com/octylFractal/91ae953d6a6f3fe757277c31ae495aed
* I couldn't find any upstream bug info.

Steps to reproduce:
1. Run `atom --safe .`
2. Wait until it crashes, takes about 10 seconds.

I could reproduce this on two of my Arch Linux computers. Unsure if it's a distro issue or not.
This task depends upon

Closed by  Caleb Maclennan (alerque)
Thursday, 07 April 2022, 14:15 GMT
Reason for closing:  Fixed
Additional comments about closing:  atom-1.61.0beta0-1
Comment by Rome R. (mDuo13) - Wednesday, 02 March 2022, 23:24 GMT
After doing a system upgrade yesterday this is happening to me too.

I've attached a log showing the errors that get printed to console during the crash.
   atom-crash.log (2.5 KiB)
Comment by Ishaan Bhimwal (ishaanbhimwal) - Saturday, 05 March 2022, 13:05 GMT
Try launching atom with the "--no-sandbox" flag. If this works then you can edit "/usr/share/application/atom.desktop" and include it in the "Exec" line.

See relevant forum post https://bbs.archlinux.org/viewtopic.php?pid=2025510#p2025510.
Comment by Octavia Togami (octylFractal) - Saturday, 05 March 2022, 17:18 GMT
That does work for me, thanks.
Comment by loqs (loqs) - Sunday, 13 March 2022, 02:10 GMT
Updating the PKGBUILD to the 1.60 switched to electron11 which it is not supposed to support and I can no longer reproduce the issue.
Comment by loqs (loqs) - Sunday, 20 March 2022, 21:18 GMT
diff's that might help anyone wanting to maintain the packages in AUR [1].

[1] https://lists.archlinux.org/pipermail/arch-dev-public/2022-March/030761.html
   PKGBUILD.atom.diff (6.2 KiB)
   PKGBUILD.electron11.diff (20.6 KiB)
   PKGBUILD.apm.diff (9.7 KiB)
Comment by Caleb Maclennan (alerque) - Thursday, 07 April 2022, 11:44 GMT
@loqs Thanks for those patches! Even if I couldn't apply them directly because I was taking a different approach to some of the issues they were quite helpfull in getting the packages actually working and I think I've just about got new Atom pakcages to post!
Comment by loqs (loqs) - Thursday, 07 April 2022, 12:32 GMT
@alerque glad they helped. This is updated for the current atom PKGBUILD.

_electron_version was being set before electron11 was installed so I moved that to prepare and duplicated it in build.
I kept package-lock.json as the build worked with it and would then be reproducible.
I moved apm install back into build as it is building native modules and Arch's build flags are not set in prepare. Something disliked fexceptions so remove that from CXXFLAGS.
GYP_DEFINES="openssl_fips=" until config.gpyi is fixed for https://github.com/nodejs/node-gyp/pull/2497 or you find where to add --force-process-config
Edit:
It is https://github.com/atom/watcher that breaks with fexceptions src/worker/linux/cookie_jar.h
Cookie(ChannelID channel_id, std::string &&from_path, EntryKind kind);
missing noexcept while the implementation has noexcept.


   PKGBUILD.diff (1.9 KiB)

Loading...