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 1804171 - Fix major bug in primary keys handling
Summary: Fix major bug in primary keys handling
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: gom
Version: 8.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: 8.0
Assignee: Bastien Nocera
QA Contact: Desktop QE
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-02-18 11:38 UTC by Bastien Nocera
Modified: 2020-11-04 02:31 UTC (History)
2 users (show)

Fixed In Version: gom-0.4-1.el8
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-11-04 02:31:19 UTC
Type: Bug
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2020:4631 0 None None None 2020-11-04 02:31:22 UTC

Description Bastien Nocera 2020-02-18 11:38:24 UTC
This would be done by updating to gom 0.4

See:
https://mail.gnome.org/archives/distributor-list/2020-February/msg00004.html

Comment 1 Tomas Pelka 2020-03-18 20:36:17 UTC
Bastien is there any way how to explicitly trigger the issue, or is there e.g. test within gom test suite that would test it?

Thanks
-Tom

Comment 2 Bastien Nocera 2020-03-19 10:50:36 UTC
(In reply to Tomas Pelka from comment #1)
> Bastien is there any way how to explicitly trigger the issue, or is there
> e.g. test within gom test suite that would test it?

There aren't any specific gom tests, but it's obvious when using a newer glib. It will assert() when running the existing tests under the new glib, without the fixes.

Comment 3 Bastien Nocera 2020-04-03 12:28:24 UTC
Fixed in gom-0.4-1.el8

Comment 10 errata-xmlrpc 2020-11-04 02:31:19 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 (gom bug fix and enhancement update), 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-2020:4631


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