Bug 1322950 - mountain-crossing.png file corrupt in f22-backgrounds-extras package
Summary: mountain-crossing.png file corrupt in f22-backgrounds-extras package
Keywords:
Status: CLOSED DUPLICATE of bug 1285997
Alias: None
Product: Fedora
Classification: Fedora
Component: f22-backgrounds
Version: 22
Hardware: All
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: Martin Sourada
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-03-31 18:17 UTC by Mike Simms
Modified: 2016-04-16 05:50 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-04-16 05:50:06 UTC
Type: Bug

Attachments (Terms of Use)
screenshot illustrating problem (141.77 KB, image/png)
2016-03-31 18:17 UTC, Mike Simms 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Description Mike Simms 2016-03-31 18:17:16 UTC 
Created attachment 1142337 [details]
screenshot illustrating problem

Description of problem:The png file is corrupt so the image does not load. First noticed when using the XML slideshow in MATE and seeing blank desktop.


Version-Release number of selected component (if applicable):22.1.0.1.fc22


How reproducible: Consistent across all our installs so not a failing HDD or failed download


Steps to Reproduce:
1. Install f22-backgrounds-extras
2. Try viewing the mountain-crossing.png file in EOM or your DE's default Image Viewer or selecting for use as a background image. Neither can load it.
3.

Actual results: blank screen if using the XML slideshow. Unable to open the file with an image viewer


Expected results: Displayed correct image


Additional info:
Comment 1 Luya Tshimbalanga 2016-04-16 05:50:06 UTC 
Thank you for reporting about the bug. It turned mountain-crossing file should be in JPEG rather than PNG. I will close this bug because a similar issue was reported earlier.

*** This bug has been marked as a duplicate of bug 1285997 ***
Note You need to log in before you can comment on or make changes to this bug.