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 2094360

Summary: gpg key verification failure prevents app install from other repo
Product: Red Hat Enterprise Linux 9 Reporter: Panos Asproulis <panos.asproulis>
Component: PackageKitAssignee: Richard Hughes <rhughes>
Status: CLOSED MIGRATED QA Contact: Desktop QE <desktop-qa-list>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 9.0CC: klember, rhughes
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:52:24 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:
Attachments:
Description Flags
GNOME Software - Installation Failure none

Description Panos Asproulis 2022-06-07 13:25:57 UTC
Description of problem:

The GNOME Software application on RHEL9 does not install any RPM packages from any repository except flatpaks from the Flathub repository.

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

gnome-software-41.4-1.el9.x86_64

How reproducible:

100%

Steps to Reproduce:

1. Open GNOME Software center find an application available as an RPM package from any repository e.g. EPEL-9.

2. Click on the install button.

3. An error will appear on the screen with the message: "Unable to install <package name> as not supported". The package will not be installed.

Actual results:

The selected package is not installed.

Expected results:

The selected package is installed.

Additional info:

EPEL-9 and the Flathub repositories have been added to the system. Installation using dnf for the same RPM package works properly. Flathubs can be installed by both the GNOME Software application and by using the flatpak command.

Comment 1 Milan Crha 2022-06-07 15:20:24 UTC
Thanks for a bug report. I tried to reproduce this, but it worked as expected here. First, I chose "Ark" application, which fails to install due to dependencies (the full error is not visible in the Software [1], it's visible only on command line). Second, I chose "CopyQ" from EPEL-9 and it installed with no problem.

I think you tried to install an application, which is included in more than one repo. Can it be the reason? If so, this can be (at least partly) related to [2], for which is no upstream fix.

[1] https://gitlab.gnome.org/GNOME/gnome-software/-/merge_requests/1084
[2] https://gitlab.gnome.org/GNOME/gnome-software/-/issues/1668

Comment 2 Panos Asproulis 2022-06-08 13:42:12 UTC
Created attachment 1888053 [details]
GNOME Software - Installation Failure

Comment 3 Panos Asproulis 2022-06-08 13:43:03 UTC
I tried to install Firefox which is only available on Red Hat's repo by running gnome-software with the --verbose option to see messages on the screen. When I click the install button I get the error message that it cannot be installed as not supported and on my terminal I see the following messages:

13:28:28:0561 Gs  emitting global waiting
13:28:28:0783 Gs  emitting global querying
13:28:28:0783 Gs  emitting global downloading
13:28:31:0585 PK  remove state 0x5616f74b36e0
13:28:31:0585 Gs  recovering state on firefox.desktop from installing to available
13:28:31:0589 Gs  Disconnecting cancellable 0x7f39ac0dd360

Then I searched for the CpyQ package. It is available as either a flapak application from Flathub or an RPM application from epel-9. The flatpak version can be installed without any problems. If I choose the epel-9 version then the image of the application on the main screen of gnome-software cannot be loade and displayed as shown in the attached screenshot while on the terminal I get the error message:

13:37:25:0395 Gs  Result of screenshot downloading attempt with status code '404': Not Found

When I click on the install button the application does not install while the terminal produces the following messages:

13:38:41:0660 Gs  emitting global waiting
13:38:41:0673 Gs  emitting global querying
13:38:41:0994 Gs  emitting global downloading
13:38:42:0751 PK  remove state 0x5616fca583f0
13:38:42:0751 Gs  recovering state on com.github.hluk.copyq.desktop from installing to available
13:38:42:0752 Gs  Disconnecting cancellable 0x5616f90469e0

Comment 4 Panos Asproulis 2022-06-08 14:02:52 UTC
So, I found that the problem is caused by the official Skype repository which I have added. The repo file is the following:

[skype-stable]
name=skype (stable)
baseurl=https://repo.skype.com/rpm/stable/
enabled=1
gpgcheck=1
gpgkey=https://repo.skype.com/data/SKYPE-GPG-KEY

When gnome-software is trying to process this repository and load its contents it fails to parse the Skype GPG key file which is indeed downloaded correctly and it is perfectly fine. After this failure the GNOME Software does not work properly for RPM applications. My solution was to disable the gpgcheck option as:

gpgcheck=0

and in this case it does not try to parse the Skype GPG key file and then GNOME Software works properly. As to why it fails to parse this file, I have no idea.

Comment 5 Milan Crha 2022-06-09 05:47:03 UTC
Thanks for the update. I've been wondering whether there's anything wrong with your configured repos, but I'd not expect any such thing.

The gnome-software does not work with these files, it uses PackageKit under the hood, thus I move this to the PackageKit.

Comment 6 RHEL Program Management 2023-09-17 14:51:58 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 7 RHEL Program Management 2023-09-17 14:52:24 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.