Automatic update for firefox-142.0-3.fc43.
* Fri Aug 15 2025 Tom Stellard <tstellar@redhat.com> - 142.0-3
- Fix build with llvm-21
Updates may require up to 24 hours to propagate to mirrors. If the following command doesn't work, please retry later:
sudo dnf upgrade --refresh --advisory=FEDORA-2025-2def98c15cPlease log in to add feedback.
This update was automatically created
This update's test gating status has been changed to 'waiting'.
This update's test gating status has been changed to 'passed'.
This update has been submitted for stable by bodhi
I just upgraded to Fedora 43, and I'm seeing problems with Firefox that make it difficult to use. Sometimes, when opening secondary windows -- for example, those used when downloading files or viewing certificates -- and sometimes when dragging, resizing, or attempting to close the Firefox main windows, the foremost window will suddenly become either transparent or dark and opaque, often with a laddering effect, and decorations like the title bar and closure buttons will disappear. The browser becomes unresponsive, and must be forcefully restarted. This does not happen all of the time, but often enough that the browser is hamstrung. It happens with both firefox-142.0-3.fc43 and firefox-142.0.1-1.fc43, with both kernels 6.16.4-200.fc42 and 6.17.0-0.rc3.31.fc43, with both mesa-25.1.4-2.fc43 and mesa-25.2.1-1.fc44, and on the Plasma, Gnome, and Gnome Classic desktops. I'm using the amdgpu graphics driver with an AMD Bonaire GPU on x86_64. This did not occur on Fedora 42.
Please report that at https://bugzilla.mozilla.org/ component Core : widget/gtk. will look at it.
The problem is still there with gnome 49.rc and mesa 25.2.2-1.fc44. I'm trying to find if it is in part due to my local configuration. When it happens, I'm seeing repetitive error messages of the kind:
I've also noticed that WebRender is failing to initialize properly at times, forcing a fallback to software rendering. This does not happen all of the time. The reasons giving in about:support for the failure include at least two different error codes -- I'll let you know which codes after I reproduce them again.
I had to take a unpleasant detour down the glib2 problem rabbit-hole, but here is some more preliminary info:
One of the error codes causing a fallback to painfully slow software rendering:
Decision Log HW_COMPOSITING: default: available, runtime: unavailable, WebRender initialization failed, Blocklisted; failure code wr_window_new: MaxTextureSize_POST ... Failure Log (#0) Error: RenderCompositorSWGL failed mapping default framebuffer, no dt (#24) Error: Detect DeviceReset DeviceResetReason::UNKNOWN DeviceResetDetectPlace::WR_POST_UPDATE in Parent process (#25) Error: Detect DeviceReset DeviceResetReason::UNKNOWN DeviceResetDetectPlace::WR_POST_UPDATE in Parent process (#26) Error: Detect DeviceReset DeviceResetReason::UNKNOWN DeviceResetDetectPlace::WR_POST_UPDATE in Parent process (#27) Error: Detect DeviceReset DeviceResetReason::UNKNOWN DeviceResetDetectPlace::WR_POST_UPDATE in Parent process (#28) Error: Detect DeviceReset DeviceResetReason::UNKNOWN DeviceResetDetectPlace::WR_POST_UPDATE in Parent process (#29) Error: Detect DeviceReset DeviceResetReason::UNKNOWN DeviceResetDetectPlace::WR_POST_UPDATE in Parent process (#30) Error: Detect DeviceReset DeviceResetReason::UNKNOWN DeviceResetDetectPlace::WR_POST_UPDATE in Parent process (#31) Error: Detect DeviceReset DeviceResetReason::UNKNOWN DeviceResetDetectPlace::WR_POST_UPDATE in Parent process (#32) Error: Detect DeviceReset DeviceResetReason::UNKNOWN DeviceResetDetectPlace::WR_POST_UPDATE in Parent process (#33) Error: Detect DeviceReset DeviceResetReason::UNKNOWN DeviceResetDetectPlace::WR_POST_UPDATE in Parent process (#34) Error: Device reporting insufficient max texture size (0) (#35) Error: wr_window_new: MaxTextureSize (#36) Error: Failed to connect WebRenderBridgeChild. isParent=true (#37) Error: Fallback WR to SW-WR (#38) Error: Detect DeviceReset DeviceResetReason::UNKNOWN DeviceResetDetectPlace::WR_POST_UPDATE in Parent process
Other miscellaneous problems:
[SELinux hiccups, even though I've disabled widevine...]
restorecon: SELinux: Could not get canonical path for /home/bmf/.mozilla/firefox//gmp-widevinecdm/ restorecon: No such file or directory. [198513] Sandbox: seccomp sandbox violation: pid 198513, tid 198513, syscall 16, args 2 2150388778 140726647389680 0 139907859371040 0. [GFX1-]: RenderCompositorSWGL failed mapping default framebuffer, no dt ...@localhost:/tmp:Fri Sep 05 16:58:49:14:0$[198817] Sandbox: seccomp sandbox violation: pid 198817, tid 198817, syscall 16, args 2 2150388778 140726647394208 0 139907960968224 0. [GFX1-]: Detect DeviceReset DeviceResetReason::UNKNOWN DeviceResetDetectPlace::WR_POST_UPDATE in Parent process [GFX1-]: Detect DeviceReset DeviceResetReason::UNKNOWN DeviceResetDetectPlace::WR_POST_UPDATE in Parent process [GFX1-]: Failed to connect WebRenderBridgeChild. isParent=false ...
and a crash:
https://crash-stats.mozilla.org/report/index/bp-2e48e853-9f88-4e5b-b329-5ba3e0250906
That may be https://bugzilla.mozilla.org/show_bug.cgi?id=1986254 - looks like AMD drivers issue.
I'm certainly seeing some similar problems. I've set widget.wayland.fractional-scale.enabled=true, and as yet I haven't seen the MaxTextureSize problem again, but the other problems continue, frequently:
restorecon: SELinux: Could not get canonical path for /home/bmf/.mozilla/firefox/*/gmp-widevinecdm/* restorecon: No such file or directory. [20432] Sandbox: seccomp sandbox violation: pid 20432, tid 20432, syscall 16, args 2 2150388778 140724106651312 0 140013312017440 0. [20685] Sandbox: seccomp sandbox violation: pid 20685, tid 20685, syscall 16, args 2 2150388778 140724106651312 0 140013337629728 0. [GFX1-]: RenderCompositorSWGL failed mapping default framebuffer, no dt [GFX1-]: Detect DeviceReset DeviceResetReason::UNKNOWN DeviceResetDetectPlace::WR_POST_UPDATE in Parent process [GFX1-]: Detect DeviceReset DeviceResetReason::UNKNOWN DeviceResetDetectPlace::WR_POST_UPDATE in Parent process [GFX1-]: Detect DeviceReset DeviceResetReason::UNKNOWN DeviceResetDetectPlace::WR_POST_UPDATE in Parent process [GFX1-]: Failed to connect WebRenderBridgeChild. isParent=false [GFX1-]: Failed to connect WebRenderBridgeChild. isParent=false [GFX1-]: Failed to connect WebRenderBridgeChild. isParent=false [GFX1-]: Failed to connect WebRenderBridgeChild. isParent=false [GFX1-]: Failed to connect WebRenderBridgeChild. isParent=false [GFX1-]: Detect DeviceReset DeviceResetReason::UNKNOWN DeviceResetDetectPlace::WR_POST_UPDATE in Parent process [GFX1-]: Detect DeviceReset DeviceResetReason::UNKNOWN DeviceResetDetectPlace::WR_POST_UPDATE in Parent process [GFX1-]: Detect DeviceReset DeviceResetReason::UNKNOWN DeviceResetDetectPlace::WR_POST_UPDATE in Parent process [GFX1-]: Detect DeviceReset DeviceResetReason::UNKNOWN DeviceResetDetectPlace::WR_POST_UPDATE in Parent process [GFX1-]: Detect DeviceReset DeviceResetReason::UNKNOWN DeviceResetDetectPlace::WR_POST_UPDATE in Parent process [GFX1-]: Detect DeviceReset DeviceResetReason::UNKNOWN DeviceResetDetectPlace::WR_POST_UPDATE in Parent process [GFX1-]: Detect DeviceReset DeviceResetReason::UNKNOWN DeviceResetDetectPlace::WR_POST_UPDATE in Parent process [GFX1-]: Detect DeviceReset DeviceResetReason::UNKNOWN DeviceResetDetectPlace::WR_POST_UPDATE in Parent process [GFX1-]: Detect DeviceReset DeviceResetReason::UNKNOWN DeviceResetDetectPlace::WR_POST_UPDATE in Parent process [GFX1-]: Detect DeviceReset DeviceResetReason::UNKNOWN DeviceResetDetectPlace::WR_POST_UPDATE in Parent process [GFX1-]: Detect DeviceReset DeviceResetReason::UNKNOWN DeviceResetDetectPlace::WR_POST_UPDATE in Parent process [GFX1-]: Detect DeviceReset DeviceResetReason::UNKNOWN DeviceResetDetectPlace::WR_POST_UPDATE in Parent process [GFX1-]: Detect DeviceReset DeviceResetReason::UNKNOWN DeviceResetDetectPlace::WR_POST_UPDATE in Parent process [GFX1-]: Detect DeviceReset DeviceResetReason::UNKNOWN DeviceResetDetectPlace::WR_POST_UPDATE in Parent process [GFX1-]: Detect DeviceReset DeviceResetReason::UNKNOWN DeviceResetDetectPlace::WR_POST_UPDATE in Parent process [GFX1-]: Detect DeviceReset DeviceResetReason::UNKNOWN DeviceResetDetectPlace::WR_POST_UPDATE in Parent process [GFX1-]: Detect DeviceReset DeviceResetReason::UNKNOWN DeviceResetDetectPlace::WR_POST_UPDATE in Parent process [GFX1-]: Detect DeviceReset DeviceResetReason::UNKNOWN DeviceResetDetectPlace::WR_POST_UPDATE in Parent process [GFX1-]: Detect DeviceReset DeviceResetReason::UNKNOWN DeviceResetDetectPlace::WR_POST_UPDATE in Parent process [GFX1-]: Detect DeviceReset DeviceResetReason::UNKNOWN DeviceResetDetectPlace::WR_POST_UPDATE in Parent process [GFX1-]: Detect DeviceReset DeviceResetReason::UNKNOWN DeviceResetDetectPlace::WR_POST_UPDATE in Parent process [GFX1-]: Detect DeviceReset DeviceResetReason::UNKNOWN DeviceResetDetectPlace::WR_POST_UPDATE in Parent process [GFX1-]: Detect DeviceReset DeviceResetReason::UNKNOWN DeviceResetDetectPlace::WR_POST_UPDATE in Parent process [GFX1-]: Detect DeviceReset DeviceResetReason::UNKNOWN DeviceResetDetectPlace::WR_POST_UPDATE in Parent process [GFX1-]: Detect DeviceReset DeviceResetReason::UNKNOWN DeviceResetDetectPlace::WR_POST_UPDATE in Parent process [GFX1-]: Detect DeviceReset DeviceResetReason::UNKNOWN DeviceResetDetectPlace::WR_POST_UPDATE in Parent process [GFX1-]: Detect DeviceReset DeviceResetReason::UNKNOWN DeviceResetDetectPlace::WR_POST_UPDATE in Parent process [GFX1-]: Detect DeviceReset DeviceResetReason::UNKNOWN DeviceResetDetectPlace::WR_POST_UPDATE in Parent process [GFX1-]: Detect DeviceReset DeviceResetReason::UNKNOWN DeviceResetDetectPlace::WR_POST_UPDATE in Parent process [GFX1-]: Detect DeviceReset DeviceResetReason::UNKNOWN DeviceResetDetectPlace::WR_POST_UPDATE in Parent process Exiting due to channel error. Exiting due to channel error. Exiting due to channel error. Exiting due to channel error. Exiting due to channel error. Exiting due to channel error. Exiting due to channel error. Exiting due to channel error. Exiting due to channel error. Exiting due to channel error. Exiting due to channel error. Exiting due to channel error. Exiting due to channel error. [GFX1-]: CompositorBridgeChild receives IPC close with reason=AbnormalShutdown Exiting due to channel error. Exiting due to channel error. Exiting due to channel error. Exiting due to channel error. Exiting due to channel error. Exiting due to channel error.In most cases this causes the browser to become unresponsive, requiring a forceful restart, as before. What additional information can I provide that might be helpful in debugging, and how can I obtain it?
https://bugzilla.mozilla.org/show_bug.cgi?id=1986254 is the right place where do direct your issues. This is package update system, not bug tracking one.
Also MESA tracker is the correct place where to report gfx issues on AMD - https://gitlab.freedesktop.org/mesa/mesa/-/issues
Okay, I'll provide information in the mesa issue 13877 when they've recovered from the DDoS attack.