Bug 2110527 - Files in f36-backgrounds-base rpm with .png file extension are JPEGs
Summary: Files in f36-backgrounds-base rpm with .png file extension are JPEGs
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: f36-backgrounds
Version: 36
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Luya Tshimbalanga
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-07-25 14:29 UTC by Thomas Jarosch
Modified: 2023-05-25 17:43 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: ---
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-05-25 17:43:38 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Thomas Jarosch 2022-07-25 14:29:35 UTC
Description of problem:

The files in the /usr/share/backgrounds/f36/default/ directory with a .png file extension are actually JPEGs.

$ file *
f36-01-day.png:   JPEG image data, JFIF standard 1.01, resolution (DPI), density 300x300, segment length 16, Exif Standard: [TIFF image data, little-endian, direntries=12, description=II*, orientation=upper-left, xresolution=158, yresolution=166, resolutionunit=2, software=darktable 3.6.1, datetime=2022:03:17 15:43:21], baseline, precision 8, 4032x3024, components 3

f36-02-night.png: JPEG image data, JFIF standard 1.01, resolution (DPI), density 300x300, segment length 16, Exif Standard: [TIFF image data, little-endian, direntries=12, description=II*, orientation=upper-left, xresolution=158, yresolution=166, resolutionunit=2, software=darktable 3.6.1, datetime=2022:03:17 15:50:51], baseline, precision 8, 4032x3024, components 3


KDE's kdm login manager refuses to load those and shows a black background instead:

$ grep background /var/log/kdm.log
kdmgreet(4384) KdmPixmap::loadPixmap: failed to load "/usr/share/backgrounds/default.png"


Version-Release number of selected component (if applicable):
36.1.1

How reproducible:

Download the current f36-backgrounds-base package from Koji and inspect the files: https://kojipkgs.fedoraproject.org//packages/f36-backgrounds/36.1.1/1.fc36/noarch/f36-backgrounds-base-36.1.1-1.fc36.noarch.rpm

-> someone saved JPEGs with a .png file extension. Files were correct PNGs on F34 f.e.


My local fix:

Converted those files to real PNGs via gimp. Now kdm also shows the login background picture.

Comment 1 Thomas Jarosch 2022-07-25 14:38:30 UTC
Version 36.0.2 still contained PNGs, the JPEGs were "introduced" in version 36.1.0.

(quickly downloaded them from Koji and browsed the rpm via "mc")

Comment 2 Ben Cotton 2023-04-25 17:39:27 UTC
This message is a reminder that Fedora Linux 36 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora Linux 36 on 2023-05-16.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
'version' of '36'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, change the 'version' 
to a later Fedora Linux version. Note that the version field may be hidden.
Click the "Show advanced fields" button if you do not see it.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora Linux 36 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora Linux, you are encouraged to change the 'version' to a later version
prior to this bug being closed.

Comment 3 Ludek Smid 2023-05-25 17:43:38 UTC
Fedora Linux 36 entered end-of-life (EOL) status on 2023-05-16.

Fedora Linux 36 is no longer maintained, which means that it
will not receive any further security or bug fix updates. As a result we
are closing this bug.

If you can reproduce this bug against a currently maintained version of Fedora Linux
please feel free to reopen this bug against that version. Note that the version
field may be hidden. Click the "Show advanced fields" button if you do not see
the version field.

If you are unable to reopen this bug, please file a new report against an
active release.

Thank you for reporting this bug and we are sorry it could not be fixed.


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