Bug 2221431

Summary: KDE Qt Patch collection for qt5-qtimageformats
Product: [Fedora] Fedora Reporter: Joshua Goins <josh>
Component: qt5-qtimageformatsAssignee: Than Ngo <than>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 38CC: jgrulich, jreznik, kde-sig, rdieter, than
Target Milestone: ---Keywords: Desktop
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: qt5-qtimageformats-5.15.10-2.fc38 Doc Type: ---
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2023-07-14 02:35:53 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Joshua Goins 2023-07-08 23:29:22 UTC
I think we're shipping the KDE Patch collection for Qt in some packages, but not for qt5-qimageformats. There are some pretty bad bugs fixed by the patchset for this component, such as https://invent.kde.org/qt/qt/qtimageformats/-/merge_requests/6/diffs - affecting WebP images in NeoChat and Tokodon.

Reproducible: Always

Comment 1 Fedora Update System 2023-07-10 07:31:16 UTC
FEDORA-2023-befa269f82 has been submitted as an update to Fedora 38. https://bodhi.fedoraproject.org/updates/FEDORA-2023-befa269f82

Comment 2 Fedora Update System 2023-07-11 01:52:18 UTC
FEDORA-2023-befa269f82 has been pushed to the Fedora 38 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2023-befa269f82`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2023-befa269f82

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 3 Fedora Update System 2023-07-14 02:35:53 UTC
FEDORA-2023-befa269f82 has been pushed to the Fedora 38 stable repository.
If problem still persists, please make note of it in this bug report.