I'm running Fedora Linux 41 on an Intel(R) Pentium(R) CPU G2030 @ 3.00GHz machine. Its window manager is (non-Wayland) Xfce. After updating from: chromium-137.0.7151.103-1.fc41.x86_86 to: chromium-138.0.7204.49-1.fc41.x86_86 ...it will no longer start. Trying to start it from the command line: $ chromium-browser about:blank Illegal instruction (core dumped) ...but no vmcore is left in my $HOME or /tmp. Updating to chromium-138.0.7204.100-1.fc41.x86_86 did not resolve the issue. I've read that "Illegal instruction" means that a CPU instruction was executed that is not valid for my CPU. I've looked through Chrome's release notes but nothing stands out as a possible cause. As a final data point, I'm also running Fedora Linux 41 on a AMD Ryzen 7 PRO 8840HS w/ Radeon 780M Graphics (again with non-Wayland Xfce) and Chromium works fine there. So again I'm wondering if there is something about my old Intel CPU causing Chromium to crash. Reproducible: Always
Is https://discussion.fedoraproject.org/t/where-is-chromiums-debuginfo-package/159053 an example of this?
(In reply to Mr. Beedell, Roke Julian Lockhart (RJLB) from comment #3) === > Is > https://discussion.fedoraproject.org/t/where-is-chromiums-debuginfo-package/ > 159053 an example of this? === I do not think so. My strace output (which has been attached to this Bugzilla ticket as a private attachment) shows: --- SIGILL {si_signo=SIGILL, si_code=ILL_ILLOPN, si_addr=0x7fa01939439d} --- +++ killed by SIGILL (core dumped) +++ ...and it and my abrt output does not mention anything about the need for debug packages or symbols.
Created attachment 2107032 [details] Strace from running /usr/lib64/chromium-browser/chromium-browser (139.0.7258.127-1.fc41.x86_64) on 2025-09-19. I've had to put this problem aside for the past ~9 weeks, but today I came back to it. I'm happy to report that some update has fixed the problem. Today I tried running Chromium (139.0.7258.127-1.fc41.x86_64) and it still failed. (See chromium_broken.debug.) I then updated my test server, resulting in these new packages: libavcodec-7.1.2-1.fc41.x86_64.rpm libavdevice-7.1.2-1.fc41.x86_64.rpm libavfilter-7.1.2-1.fc41.x86_64.rpm libavformat-7.1.2-1.fc41.x86_64.rpm libavutil-7.1.2-1.fc41.x86_64.rpm libpostproc-7.1.2-1.fc41.x86_64.rpm libswresample-7.1.2-1.fc41.x86_64.rpm libswscale-7.1.2-1.fc41.x86_64.rpm nvidia-libXNVCtrl-580.82.09-1.fc41.x86_64.rpm bind-libs-9.18.39-3.fc41.1.x86_64.rpm chromium-140.0.7339.127-1.fc41.x86_64.rpm chromium-common-140.0.7339.127-1.fc41.x86_64.rpm cups-libs-2.4.14-1.fc41.x86_64.rpm kernel-6.16.7-100.fc41.x86_64.rpm kernel-core-6.16.7-100.fc41.x86_64.rpm kernel-modules-6.16.7-100.fc41.x86_64.rpm kernel-modules-core-6.16.7-100.fc41.x86_64.rpm kernel-modules-extra-6.16.7-100.fc41.x86_64.rpm libadwaita-1.6.9-1.fc41.x86_64.rpm libarrow-16.1.0-15.fc41.x86_64.rpm libarrow-acero-libs-16.1.0-15.fc41.x86_64.rpm libarrow-dataset-libs-16.1.0-15.fc41.x86_64.rpm libarrow-doc-16.1.0-15.fc41.noarch.rpm libcloudproviders-0.3.6-1.fc41.x86_64.rpm libgexiv2-0.14.6-1.fc41.x86_64.rpm libklvanc-1.6.0-1.fc41.x86_64.rpm libldb-4.21.8-1.fc41.x86_64.rpm libopenmpt-0.8.3-1.fc41.x86_64.rpm liborc2-2.0.6-1.fc41.x86_64.rpm libsmbclient-4.21.8-1.fc41.x86_64.rpm libsoup3-3.6.5-7.fc41.x86_64.rpm libwbclient-4.21.8-1.fc41.x86_64.rpm openxr-libs-1.1.51-1.fc41.x86_64.rpm ostree-libs-2025.6-1.fc41.x86_64.rpm parquet-libs-16.1.0-15.fc41.x86_64.rpm samba-client-libs-4.21.8-1.fc41.x86_64.rpm samba-common-libs-4.21.8-1.fc41.x86_64.rpm tesseract-libs-5.4.1-7.fc41.x86_64.rpm wireplumber-libs-0.5.11-1.fc41.x86_64.rpm zbar-libs-0.23.93-9.fc41.x86_64.rpm x265-libs-4.1-4.fc41.x86_64.rpm xevd-libs-0.5.0-1.fc41.x86_64.rpm xeve-libs-0.5.1-1.fc41.x86_64.rpm I then rebooted and tried again. This time it worked. (See chromium_working.debug.) I will now close this Bugzilla ticket. Thanks for the encouragement on what to do... though I never got around to doing it. I'm sorry I had to put the problem aside for so long.
Created attachment 2107033 [details] Strace from running /usr/lib64/chromium-browser/chromium-browser (140.0.7339.127-1.fc41.x86_64) on 2025-09-19.