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 1445651 - gnome-session: (org.gnome.Software:2457): Gs-WARNING **: failed to download: The package id's '' are not valid
Summary: gnome-session: (org.gnome.Software:2457): Gs-WARNING **: failed to download: ...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: gnome-software
Version: 7.3
Hardware: All
OS: Linux
medium
high
Target Milestone: rc
: ---
Assignee: Richard Hughes
QA Contact: Desktop QE
URL:
Whiteboard:
Depends On:
Blocks: 1420851 1479818
TreeView+ depends on / blocked
 
Reported: 2017-04-26 08:48 UTC by JongYoung Moon
Modified: 2021-06-10 12:15 UTC (History)
7 users (show)

Fixed In Version: gnome-software-3.22.7-2.el7
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-04-10 13:55:50 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Knowledge Base (Solution) 3173111 0 None None None 2017-10-24 01:21:27 UTC
Red Hat Product Errata RHBA-2018:0803 0 None None None 2018-04-10 13:56:17 UTC

Description JongYoung Moon 2017-04-26 08:48:13 UTC
* Description of problem:
gnome-session: (org.gnome.Software:2457): Gs-WARNING **: failed to download: The package id's '' are not valid
- Above logs are persistently logged

* Version-Release number of selected component (if applicable):
Red Hat Enterprise Linux 7.3

* How reproducible:
Always happen when installing Desktop Environment in RHEL 7.3

* Steps to Reproduce:
1. Install RHEL with GNOME Desktop Environment
2. Login

* Actual results:
gnome-session: (org.gnome.Software:2457): Gs-WARNING **: failed to download: The package id's '' are not valid
- Above logs are persistently logged

* Expected results:
gnome-session: (org.gnome.Software:2457): Gs-WARNING **: failed to download: The package id's '' are not valid
- Above logs would not be logged

* Additional info:
As far as investigate it in the following url, it looks it's caused by bug of libhif library. workaround is just running 'pkcon repair' and then rebooting system.

http://fedoraproject.org/wiki/Common_F21_bugs#libhif-packagekit-broken

I expect backport from fedora is required

Comment 11 errata-xmlrpc 2018-04-10 13:55:50 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, 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-2018:0803


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