Works fine for the issue mentioned in the details!.

@ciupicri, just out of curiosity, why are you using the X intel driver and not just use the modesetting that is bundled in the X.org server? That driver module is basically abandoned and deprecated in favor of modesetting + kms.

@ciupicri I made a typo in the SPEC file of xorg-x11-drv-intel when switching to meson. Thanks for reporting.

As stated in the bug, I've rebuilt libheif in my repository with the updated OpenJPH, the issue should be gone now.

Hello, since you mentioned having it installed from fedora-multimedia, can you try installing this update here in bodhi and libheif from fedora as well? i think that is an issue when libheif is being loaded by other programs and then in turn loading libopenjph. An alternative is to move the file /usr/lib64/libheif/libheif-jphenc.so away and check if it's happening again.

Being a completely new package with nothing in Fedora depending on it, it should not trigger any crash whatsoever.

btw: https://pkgs.rpmfusion.org/cgit/nonfree/xorg-x11-drv-nvidia.git/commit/

These libraries are the same as what is shipped by the driver. It's up to the driver packager to decide if they want to use these or the bundled ones.

Having said that, you should not have the issue in the first place since these libraries are useless if the driver does not pull them in as a a dependency, Why are you installing them?

@anotheruser Super, I've asked Austin to merge the change and then I will rebase the udpate.

@anotheruser please let me know if the pr fixes it for you with the currently packaged Firefox in Fedora.

@anotheruser I've removed the automatic pushing to stable to collect some more feedback (I'm on 560 now). I can confirm that pr #124 has not been applied internally by Austin yet.

@anotheruser this should contain the fixes for the Firefox crashes you experienced in the other update. The same library is being included in the 560.31.02 driver build.

I don't have any Firefox crash so far on Wayland.

Works fine! (no RPMFusion).

Fixes https://bugzilla.redhat.com/show_bug.cgi?id=2283639. No longer throwing up the error.