Bug 2175089

Summary:	GNOME Software lists applications with "NoDisplay=true" in their .desktop files
Product:	Red Hat Enterprise Linux 9	Reporter:	Tomas Popela <tpopela>
Component:	appstream-data	Assignee:	Richard Hughes <rhughes>
Status:	CLOSED MIGRATED	QA Contact:	Vera Budikova <vbudikov>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	9.1	CC:	jkoten, sbarcomb, tpelka
Target Milestone:	rc	Keywords:	MigratedToJIRA
Target Release:	---	Flags:	pm-rhel: mirror+
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2023-09-18 10:59:43 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 Tomas Popela 2023-03-03 07:56:22 UTC

In bug 2170842 it was uncovered that users are able to install LibreOffice through GNOME Software on aarch64 even though the LibreOffice is shipped without GUI to cover only headless use-cases (on s390x as well) as opposed to other architectures that contain the GUI as well. The .desktop files on aarch64 and s390x contain "NoDisplay=true" in the .desktop files which generally should be enough for appstream-builder to not populate the metadata that are later used in GNOME Software for the applications availability. The problem as uncovered by Richard is that currently appstream-data is build as a noarch package - https://gitlab.com/redhat/centos-stream/rpms/appstream-data/-/blob/e9fd1ad9a6cdc300be95c8fcf5322305f2d4f1f3/appstream-data.spec#L9 - so it doesn't have any notion about these arch specific differences. The solution might be to build appstream-data as a archful package which has its downsides as well.

Comment 1 Richard Hughes 2023-03-03 11:23:02 UTC

FWIW, the downside seems to be 4x the download, storage size and processing time for metadata regeneration -- but is probably the correct fix. We should probably do the same thing for Fedora too.

Comment 4 RHEL Program Management 2023-09-18 10:58:11 UTC

Issue migration from Bugzilla to Jira is in process at this time. This will be the last message in Jira copied from the Bugzilla bug.

Comment 5 RHEL Program Management 2023-09-18 10:59:43 UTC

This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there.

Due to differences in account names between systems, some fields were not replicated.  Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information.

To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "RHEL-" followed by an integer.  You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like:

"Bugzilla Bug" = 1234567

In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information.