Fedora Account System
Red Hat Associate
Red Hat Customer
Description of problem: Firefox coredumps when launched after booting. Firefox will still start and function normally so marked as medium severity. But the coredump is consistent. Version-Release number of selected component (if applicable): firefox-106.0.1-1.fc37.x86_64 xorg-x11-drv-nvidia-cuda-libs-520.56.06-1.fc37.x86_64 xorg-x11-drv-nvidia-libs-520.56.06-1.fc37.x86_64 xorg-x11-drv-nvidia-kmodsrc-520.56.06-1.fc37.x86_64 akmod-nvidia-520.56.06-1.fc37.x86_64 nvidia-settings-520.56.06-1.fc37.x86_64 xorg-x11-drv-nvidia-power-520.56.06-1.fc37.x86_64 xorg-x11-drv-nvidia-520.56.06-1.fc37.x86_64 nvidia-persistenced-520.56.06-1.fc37.x86_64 xorg-x11-drv-nvidia-cuda-520.56.06-1.fc37.x86_64 kmod-nvidia-6.0.6-300.fc37.x86_64-520.56.06-1.fc37.x86_64 mesa-va-drivers-22.2.2-1.fc37.x86_64 How reproducible: After every boot/reboot when first launching firefox. Possibly everytime firefox starts when not already a running process. Steps to Reproduce: 1. Boot/reboot 2. Launch firefox 3. Actual results: Firefox coredump Firefox starts and appears to run normally Expected results: Firefox runs normally; no coredump Additional info: Nov 06 07:48:24 pico systemd-coredump[6667]: [🡕] Process 6664 (firefox) of user 1000 dumped core. Module linux-vdso.so.1 with build-id 3c0956f8d5475deecc44660b2bbd2c4190dc382d Module libGLdispatch.so.0 with build-id d8a129c7b6e51a420d6135684ac6d703a08a0268 Metadata for module libGLdispatch.so.0 owned by FDO found: { "type" : "rpm", "name" : "libglvnd", "version" : "1.5.0-1.fc37", "architecture" : "x86_64", "osCpe" : "cpe:/o:fedoraproject:fedora:37" } .... Nov 06 07:48:24 pico systemd[1]: systemd-coredump: Deactivated successfully. Nov 06 07:48:24 pico firefox.desktop[6612]: [GFX1-]: glxtest: VA-API test failed: process crashed. Please check your VA-API drivers.
I forgot to note: 1. This has been consistent since I started using F37 about 3 weeks ago. 2. Today for the first time Abrt Analytics displayed an error. Clicked Report but usual, the Abrt never completes analysis. thanks
Update. This bug shows up when firefox is started on F37. Not just after rebooting/booting. thanks
Can you attach backtrace of the crash? From `coredumpctl dump` command. Thanks.
After boot this morning: Nov 07 06:56:35 pico abrt-notification[5637]: [🡕] Process 6664 (firefox) crashed in XDisplayString() Used this command: sudo coredumpctl dump 6664 --output ffdump Resulting file is too large to upload to bugzilla. What would be a good alternative? Please let me know if this is not correct. thanks
Please attach as text file. Don't use --output, run `coredumpctl dump 6664 > log.txt 2>&1` and attach log.txt here.
Created attachment 1923111 [details] coredump backtrace Used: [bgsmith@pico f]$ coredumpctl list --since=today Journal file /var/log/journal/d7b4655d38a141ee9223193fa4d35ea4/system~ is truncated, ignoring file. TIME PID UID GID SIG COREFILE EXE > Tue 2022-11-08 06:39:47 PST 3858 1000 1000 SIGSEGV present /usr/lib64/firefox/firef> [bgsmith@pico f]$ coredumpctl dump 3858 > log.txt 2>&1 log.txt still too large to upload to bugzilla. thank you
Yes, this comes from VA-API code which crashes on NVIDIA hardware: ``` #0 0x00007f163ec3d1c4 XDisplayString (libX11.so.6 + 0x311c4) #1 0x00007f163db89349 __vaDriverInit_1_15 (nvidia_drv_video.so + 0xe349) #2 0x00007f16326ca3d7 va_openDriver (libva.so.2 + 0x43d7) #3 0x00007f16326d025e vaInitialize (libva.so.2 + 0xa25e) #4 0x00007f1637617521 childvaapitest (libxul.so + 0x4c17521) #5 0x00007f163761d578 childgltest (libxul.so + 0x4c1d578) #6 0x00007f163761d692 _Z20fire_glxtest_processv (libxul.so + 0x4c1d692) #7 0x00007f163760ad61 _ZN7XREMain12XRE_mainInitEPb.part.0 (libxul.so + 0x4c0ad61) #8 0x00007f1637612916 _ZN7XREMain8XRE_mainEiPPcRKN7mozilla15BootstrapConfigE (libxul.so + 0x4c12916) #9 0x00007f1637612f31 _Z8XRE_mainiPPcRKN7mozilla15BootstrapConfigE (libxul.so + 0x4c12f31) #10 0x0000557460c789ed _ZL7do_mainiPPcS0_ (firefox + 0x109ed) #11 0x0000557460c77cd4 main (firefox + 0xfcd4) #12 0x00007f1640a4b510 __libc_start_call_main (libc.so.6 + 0x27510) #13 0x00007f1640a4b5c9 __libc_start_main@@GLIBC_2.34 (libc.so.6 + 0x275c9) #14 0x0000557460c78125 _start (firefox + 0x10125) ``` We should disable this check on NVIDIA somehow.
Upstream bug: https://bugzilla.mozilla.org/show_bug.cgi?id=1799747 We should avoid testing VA-API on NVIDIA.
Thank you for the follow up. It has been largely invisible unless I happen to be monitoring journalctl. Abrt is hit or miss on generating an alert.
This message is a reminder that Fedora Linux 37 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora Linux 37 on 2023-12-05. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a 'version' of '37'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, change the 'version' to a later Fedora Linux version. Note that the version field may be hidden. Click the "Show advanced fields" button if you do not see it. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora Linux 37 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora Linux, you are encouraged to change the 'version' to a later version prior to this bug being closed.
Fedora Linux 37 entered end-of-life (EOL) status on None. Fedora Linux 37 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora Linux please feel free to reopen this bug against that version. Note that the version field may be hidden. Click the "Show advanced fields" button if you do not see the version field. If you are unable to reopen this bug, please file a new report against an active release. Thank you for reporting this bug and we are sorry it could not be fixed.