Bug 2031998

Summary: Missing LOGO= value in os-release leads to broken branding in DEs in EPEL
Product: Red Hat Enterprise Linux 9 Reporter: Neal Gompa <ngompa13>
Component: redhat-releaseAssignee: Stephen Gallagher <sgallagh>
Status: CLOSED ERRATA QA Contact: Release Test Team <release-test-team-automation>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: CentOS StreamCC: bstinson, carl, davide, jwboyer, lisas, michel, mroche, pzatko, rdieter, sgallagh, tdawson
Target Milestone: rcKeywords: Triaged
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: redhat-release-9.0-2.12.el9 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2022-05-17 15:35:34 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Neal Gompa 2021-12-13 20:17:32 UTC
Description of problem:

A number of desktops (such as KDE Plasma, Pantheon, and others) use the LOGO= value in the os-release file to automatically pick up the correct icon for OS branding in system information applications. Fedora has this set[1], but it is missing in redhat-release and centos-release.

Please add "LOGO=fedora-logo-icon" (which is the name of the file in both redhat-logos and centos-logos as the file name is API) to the os-release file.

[1]: https://src.fedoraproject.org/rpms/fedora-release/blob/4c65215bcd6b5d9c7e87963a22d11fb80835d160/f/fedora-release.spec#_896

Comment 3 Troy Dawson 2022-01-06 18:13:35 UTC
Why "fedora-logo-icon" instead of "system-logo-icon" ?

Comment 4 Stephen Gallagher 2022-01-06 20:01:33 UTC
(In reply to Troy Dawson from comment #3)
> Why "fedora-logo-icon" instead of "system-logo-icon" ?

This filename is essentially API at this point due to too many hardcoded places that it is used.

Comment 11 errata-xmlrpc 2022-05-17 15:35:34 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (new packages: redhat-release), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2022:3893