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 1535905 - gnome-control-center crashes when a team connection with configured link-watchers is present
Summary: gnome-control-center crashes when a team connection with configured link-watc...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: NetworkManager
Version: 7.5
Hardware: Unspecified
OS: Unspecified
urgent
urgent
Target Milestone: rc
: ---
Assignee: Lubomir Rintel
QA Contact: Desktop QE
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-01-18 09:01 UTC by Francesco Giudici
Modified: 2018-04-10 13:38 UTC (History)
11 users (show)

Fixed In Version: NetworkManager-1.10.2-11.el7
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-04-10 13:37:57 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2018:0778 0 None None None 2018-04-10 13:38:33 UTC

Description Francesco Giudici 2018-01-18 09:01:32 UTC
The issue is due to a symbol clash between libjansson and libjson-glib: gnome-control-center loads libnm and libjson-glib. libnm loads libjansson. libjansson and libjson-glib have both the symbol "json_object_iter_next".

The clashing symbol is used both directly and indirectly:
* libnm uses "json_object_iter_next" directly through the macro "json_object_foreach" and "json_object_foreach_safe".
* libjansson uses the "json_object_iter_next" in many exposed APIs and links to libjson-glib symbol when called from gnome-control-center (via libnm).

The APIs that bring to the crash are called only when parsing a populated team.link-watchers property.

How reproducible:
* Create a team connection with a populated team.link-watchers property
* Try to start gnome-control-center

Comment 2 Pavlin Georgiev 2018-02-12 09:07:14 UTC
TEST SETUP
On machine qe-dell-ovs5-vm-1
under RHEL-7.5-20180201.2 x86_64 Workstation

Component version:
NetworkManager-1.10.2-11.el7

TEST PROCEDURE
* Add a new connection of type "team" and options "con-name team0 ifname nm-team autoconnect no ip4 1.2.3.4/24 connection.autoconnect-slaves yes"
* Add slave connection for master "nm-team" on device "eth1" named "team0.0"
* Bring "up" connection "team0"
* Set team.link-watchers to "ethtool" with parameters "delay-up=50", "delay-down=100"
* Bring "up" connection "team0"
* Start gnome-control-center
The bug does not appear.

RESULTS
Upgrading component: NetworkManager
to: 1.10.2-11.el7
has fixed the bug.

Comment 5 errata-xmlrpc 2018-04-10 13:37:57 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:0778


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