Description of problem: Firefox no longer starts after receiving 102.7.0-1.mga9 Version-Release number of selected component (if applicable): 102.17.0-1 How reproducible: Install latest firefox module in Cauldron hardware: Nvidia GTX1050 - using nvidia 525.85.05 proprietary driver Steps to Reproduce: 1. installed with latest updates 2. run from command line: firefox ATTENTION: default value of option mesa_glthread overridden by environment. Segmentation fault (core dumped) 3. If you want the core dump, let me know where it would dump to. I'd like to clean-up that folder anyhow.
$ rpm -q firefox firefox-102.7.0-1.mga9 $ firefox ATTENTION: default value of option mesa_glthread overridden by environment. Missing chrome or resource URL: resource://gre/modules/UpdateListener.jsm Missing chrome or resource URL: resource://gre/modules/UpdateListener.sys.mjs but it does NOT crash; and works. But I see there are updates due including kernel. Will re-try after that, but not report back if nothing changes. Have to leave this to others to help sort out.
Status: NEW => UNCONFIRMEDEver confirmed: 1 => 0
Worked fine on my AMD. So guessing related to the Nvidia proprietary driver.
I also have firefox crashing since Saturday (I update my cauldron on a daily basis). I tried: - the rpm packaged one: same error than the opener ATTENTION: default value of option mesa_glthread overridden by environment. ATTENTION: default value of option mesa_glthread overridden by environment. Erreur de segmentation (core dumped) - the vanilla version from mozilla.org: a slightly different error [GFX1-]: glxtest: VA-API test failed: process crashed. Please check your VA-API drivers. ATTENTION: default value of option mesa_glthread overridden by environment. ATTENTION: default value of option mesa_glthread overridden by environment. ExceptionHandler::GenerateDump cloned child 3707458 ExceptionHandler::SendContinueSignalToChild sent continue signal to child ExceptionHandler::WaitForContinueSignal waiting for continue signal... and a message in dmesg: [42278.706769] firefox-bin[3707388]: segfault at d8 ip 00007f34775da5f0 sp 00007fff101c7978 error 4 in libX11.so.6.4.0[7f34775c5000+87000] likely on CPU 6 (core 2, socket 0) [42278.706778] Code: 2e 0f 1f 84 00 00 00 00 00 90 8b 47 1c c3 66 66 2e 0f 1f 84 00 00 00 00 00 90 8b 47 74 c3 66 66 2e 0f 1f 84 00 00 00 00 00 90 <48> 8b 87 d8 00 00 00 c3 0f 1f 84 00 00 00 00 00 48 63 f6 48 c1 e6 My hardware is also a NVidia wit proprietary driver: Hardware: nvidia Quadro k2200 driver: dkms-nvidia-current-525.85.05-1.mga9.nonfree I've also tried using --safe-mode or with a brand new user and have the same crash
CC: (none) => stephane.pontier
Summary: Firefox core dumps on start => Firefox core dumps on start with proprietary NVIDIA moduleSource RPM: 102.7.0-1.mga9 => nvidia-current
does it help to downgrade nvidia-current to the older driver: 525.78.01 http://ftp.free.fr/mirrors/mageia.org/people/tmb/Cauldron/bugs/31442/
No, the problem persist with this version 525.78.01 of nvidia driver.
Note - changing from nvidia proprietary to nouveau driver allows firefox to function. I suspect graphics card performance is hobbled, but it is working.
Confirmed firefox segfaults my laptop using Mageia prime with nvidia current. After installing all of the packages in comment 4 using "urpmi --downgrade *.rpm" which required enabling the 32 bit repos, firefox is working (without rebooting, so it hasn't switched drivers). Running firefox under strace shows the libmesaegl1 package is the only 32 bit package being used. Restoring the nvidia drivers to current as it doesn't seem to be the drivers and then retesting firefox shows it's continuing to work. So it seems firefox on nvidia requires the 32 bit libmesaegl1 package though other 32 bit libraries ended up being installed too.
Ever confirmed: 0 => 1Status: UNCONFIRMED => NEWCC: (none) => davidwhodgins
This bug is a release blocker for Mageia 9 beta1.
Priority: Normal => release_blocker
Not so simple. Immediately after downgrading the packages, but before rebooting, firefox was working. Restoring the packages to current, firefox continued to work. Rebooting, firefox segfaults again.
Even stranger. Downgraded again, rebooted. Firefox segfaults. Installed current packages ... x11-driver-video-nvidia-current-525.85.05-1.mga9.nonfree.x86_64 2023-01-24T18:02:23 EST nvidia-current-devel-525.85.05-1.mga9.nonfree.x86_64 2023-01-24T18:02:21 EST nvidia-current-cuda-opencl-525.85.05-1.mga9.nonfree.x86_64 2023-01-24T18:02:21 EST nvidia-current-utils-525.85.05-1.mga9.nonfree.x86_64 2023-01-24T18:02:20 EST nvidia-current-lib32-525.85.05-1.mga9.nonfree.x86_64 2023-01-24T18:02:20 EST nvidia-current-doc-html-525.85.05-1.mga9.nonfree.x86_64 2023-01-24T18:02:20 EST dkms-nvidia-current-525.85.05-1.mga9.nonfree.x86_64 2023-01-24T18:00:54 EST And firefox is working again. The 32 bit libs pulled in previously are still installed.
Rebooted, and firefox continues working. I'm lost. :-(
Exiting firefox, and restarting it with no other changes and it's segfaulting again.
The workaround from the dev ml MESA_LOADER_DRIVER_OVERRIDE='kms_swrast' firefox works. Does that help pinpoint and fix the problem?
With today's mesa update firefox is working on my laptop. No workaround required. I'd like confirmation from others before closing this bug report.
Confirmed I'm using nvidia driver: # lsmod | grep nvidia nvidia_uvm 1347584 0 nvidia_drm 73728 36 drm_kms_helper 208896 1 nvidia_drm nvidia_modeset 1216512 73 nvidia_drm video 65536 1 nvidia_modeset nvidia 56393728 3605 nvidia_uvm,nvidia_modeset drm 696320 40 drm_kms_helper,nvidia,nvidia_drm Started firefox twice and browsing. Seems to be working properly now.
I also confirm that firefox works fine after updating mesa packages. Thank you
Thanks Dave, Brian and Stéphane. Closing :-)
Resolution: (none) => FIXEDStatus: NEW => RESOLVEDCC: (none) => marja11