Bug 1470633 - 'rajasthan.png' has bad JPEG artifacts
Summary: 'rajasthan.png' has bad JPEG artifacts
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: f26-backgrounds
Version: 26
Hardware: Unspecified
OS: Unspecified
unspecified
low
Target Milestone: ---
Assignee: Luya Tshimbalanga
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-07-13 10:51 UTC by Bruce Cowan
Modified: 2017-07-31 06:25 UTC (History)
3 users (show)

Fixed In Version: f26-backgrounds-26.2.7-2.fc26
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-07-31 06:25:40 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Bruce Cowan 2017-07-13 10:51:44 UTC
The 'rajasthan.png' file in the f26-backgrounds-extras-base has really obvious JPEG artifacting, and looks really poor on a large screen. This includes banding as well as the ringing artifacts associated with low quality JPEGs.

Comment 1 Luya Tshimbalanga 2017-07-13 17:11:11 UTC
Hello,
Sadly the image was originally submitted with that overlooked artefact from JPEG. Feel free to submit a fixed version so I can update it.

Comment 2 Fedora Update System 2017-07-28 03:20:24 UTC
f26-backgrounds-26.2.7-2.fc26 has been submitted as an update to Fedora 26. https://bodhi.fedoraproject.org/updates/FEDORA-2017-45d1400a33

Comment 3 Fedora Update System 2017-07-29 00:54:13 UTC
f26-backgrounds-26.2.7-2.fc26 has been pushed to the Fedora 26 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2017-45d1400a33

Comment 4 Fedora Update System 2017-07-31 06:25:40 UTC
f26-backgrounds-26.2.7-2.fc26 has been pushed to the Fedora 26 stable repository. If problems still persist, please make note of it in this bug report.


Note You need to log in before you can comment on or make changes to this bug.