RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 2031998 - Missing LOGO= value in os-release leads to broken branding in DEs in EPEL
Summary: Missing LOGO= value in os-release leads to broken branding in DEs in EPEL
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 9
Classification: Red Hat
Component: redhat-release
Version: CentOS Stream
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Stephen Gallagher
QA Contact: Release Test Team
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-12-13 20:17 UTC by Neal Gompa
Modified: 2022-05-17 15:36 UTC (History)
11 users (show)

Fixed In Version: redhat-release-9.0-2.12.el9
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-05-17 15:35:34 UTC
Type: Bug
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Gitlab redhat/centos-stream/rpms centos-release merge_requests 22 0 None None None 2021-12-13 20:23:05 UTC
Red Hat Issue Tracker RHELBLD-8505 0 None None None 2021-12-13 20:18:12 UTC
Red Hat Issue Tracker RHELPLAN-105623 0 None None None 2021-12-13 20:18:17 UTC
Red Hat Issue Tracker RTT-4109 0 None None None 2022-01-07 10:43:46 UTC
Red Hat Issue Tracker RTT-4110 0 None None None 2022-01-07 10:43:51 UTC
Red Hat Product Errata RHBA-2022:3893 0 None None None 2022-05-17 15:35:49 UTC

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


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