Chromium crashes immediately on startup with "illegal instruction". Coredump / disassembly is not really helpful and it looks like gdb is confused. But the crash does not occur with "arm64.nobti" appended to the kernel command line. which is very strong indication that chromium is not BTI ready. Following upstream bug suggests that as well: https://bugs.chromium.org/p/chromium/issues/detail?id=1145581#c60 Temporary solution would be to compile chromium with -mbranch-protection=none until the upstream issue is resolved. The solution used in https://src.fedoraproject.org/rpms/webkitgtk/pull-request/3 for the bti incompatibility in webkitgtk will probaly only work until it runs on a device with PAC. User reports are in https://discussion.fedoraproject.org/t/chromium-from-asahi-repos-crashes-everytime-on-launch-with-sigill/88281 Reproducible: Always Steps to Reproduce: 1. Install fedora-asahi-remix on a supported apple m2 device (M2 Macbook Air/Pro 13-inch) 2. install chromium 3. start chromium-browser Actual Results: chromium crashes with "illegal instruction, core dumped" Expected Results: Chromium browser starts Happens only on arm64 CPU with BTI (branch target identification) like Apple's M2.
More user reports: https://www.reddit.com/r/AsahiLinux/comments/16u9fnb/chromium_crashes_with_sigill_on_asahi_fedora_39/ This is probably be a release blocker for us, broken Chromium on half of our devices is not good...