Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
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 2097538

Summary: Screenhots in appdata reference 'master', while upstream changed the branch name to 'main'
Product: Red Hat Enterprise Linux 9 Reporter: Peter Stone <fedora-topics-562353>
Component: appstream-dataAssignee: Richard Hughes <rhughes>
Status: CLOSED MIGRATED QA Contact: Desktop QE <desktop-qa-list>
Severity: low Docs Contact:
Priority: unspecified    
Version: unspecifiedCC: klember, mcatanza, rhughes, tpopela
Target Milestone: rcKeywords: MigratedToJIRA
Target Release: ---Flags: pm-rhel: mirror+
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2023-09-17 14:55:30 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 Peter Stone 2022-06-15 22:11:58 UTC
Description of problem: There's some applications, like Evince, or Disk Usage Analyzer, where placeholder screenshots are shown instead of ones from the respective applications.


Version-Release number of selected component (if applicable): gnome-software 41.4, up to date RHEL 9.


How reproducible:


Steps to Reproduce:
1. open Software, go to Installed
2. choose Evince or Disk Usage Analyzer
3. observe that instead of expected screenshots from these programs, placeholders are shown

Actual results: placeholder image shown

Expected results: screenshots from the application to be shown

Additional info:
Machine where this occurs is connected to the Internet, is registered for updates and regular updates succeed.

Comment 1 Milan Crha 2022-06-16 06:24:41 UTC
Thanks for a bug report. It's a problem in the appstream data of the respective applications. I'll move this to the evince, open a bug to other apps as needed.

When you run gnome-software with its verbose debug mode:

   $ gnome-software --quit; gnome-software --verbose

and search for the evince and then select it, you'll see something like this:

   06:17:32:0986 Gs  Result of screenshot downloading attempt with status code '404': Not Found
   06:17:33:0046 Gs  Result of screenshot downloading attempt with status code '404': Not Found

and several lines above:

   screenshot-00:       https://gitlab.gnome.org/GNOME/evince/raw/master/data/screenshots/evince-1.png [<none>]
   screenshot-01:       https://gitlab.gnome.org/GNOME/evince/raw/master/data/screenshots/evince-2.png [<none>]

The problem is that the evince upstream renamed its `master` branch to the `main` branch, which is not reflected in the RHEL appstream data. When I change the path it finds the screenshots.

Such change might need to update RHEL package with the appstream data, I think.

Comment 2 Tomas Popela 2022-06-16 11:19:08 UTC
I suspect that more applications renamed their branch from master to main in GNOME. Michael do you have a way to find what repositories in GNOME moved from using master to main so we can look if something needs to be changed? Another option would be to ask QE to go through the applications that we have in RHEL and see whether they have screenshots available.

Comment 3 Michael Catanzaro 2022-06-16 17:18:20 UTC
(In reply to Tomas Popela from comment #2)
> I suspect that more applications renamed their branch from master to main in
> GNOME. Michael do you have a way to find what repositories in GNOME moved
> from using master to main so we can look if something needs to be changed?

Definitely not. I could only tell you about core applications tracked by release team. RHEL has way more applications than that. We need to keep up with all applications in RHEL.

It's expected that applications that delete their master branch will not have any screenshots until RHEL 10 if they stored screenshots on the master branch, which was/is best practice. That's just a predictable consequence of the ongoing branch name sabotage. As applications continue to switch branch names, more and more screenshots will disappear over time, so it's something that has to be actively kept up with. Suffice to say I'm glad I'm not maintaining our appstream data right now.

Comment 4 RHEL Program Management 2023-09-17 14:51:55 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-17 14:55:30 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.