Description of problem: After upgrading gdk-pixbuf2 to version 2.42.9-1 some JPG images can't be loaded anymore. Eog gives the error message "Error interpreting JPEG image file (Backing store not supported)". Version-Release number of selected component (if applicable): 2.42.9-1 How reproducible: Upgrade to version 2.42.9-1 of gdk-pixbuf2. Steps to Reproduce: 1. Upgrade library to 2.42.9-1 of gdk-pixbuf2. 2. Download the JPG file in the linked issue below. 3. Open the image in Eog and receive error message. Actual results: Eog shows the error message "Error interpreting JPEG image file (Backing store not supported)". Expected results: Image opens correctly. Additional info: It seems to be related to this issue https://gitlab.gnome.org/GNOME/gdk-pixbuf/-/issues/216
Worth noting that https://gitlab.gnome.org/GNOME/gdk-pixbuf/-/issues/216is marked fixed upstream as of a couple weeks ago, maybe needs a backport.
I would really appreciate if we could get a backport for this bug. I can't open a lot of my image files and the background of my desktop is also black. Thank you!
FEDORA-2022-48308bc2c4 has been submitted as an update to Fedora 36. https://bodhi.fedoraproject.org/updates/FEDORA-2022-48308bc2c4
FEDORA-2022-162412af31 has been submitted as an update to Fedora 37. https://bodhi.fedoraproject.org/updates/FEDORA-2022-162412af31
FEDORA-2022-162412af31 has been pushed to the Fedora 37 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-2022-48308bc2c4 has been pushed to the Fedora 36 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2022-48308bc2c4` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-48308bc2c4 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
Now working. Thanks!
FEDORA-2022-48308bc2c4 has been pushed to the Fedora 36 stable repository. If problem still persists, please make note of it in this bug report.