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.

Description of problem:
removing bond in networking section causes crash. Sadly gdb crashed too when I was generating backtrace so attaching just a fragment. Nevertheless, reproducer is quite straightforward.  

Version-Release number of selected component (if applicable):
control-center-3.14.4-2.el7.x86_64

How reproducible:
50%

Steps to Reproduce:
1.open control-center->network
2.click +
3.select Bond
4.Save connection
5.select created bond in left tab
6.click -

Actual results:
crash

Expected results:
no crash

Additional info:

I don't have hardware to reproduce a bonding setup. I'll need a backtrace of the crash in any case.

Created attachment 1024971 [details]
gdb backtrace fragment

(In reply to Bastien Nocera from comment #1)
> I don't have hardware to reproduce a bonding setup. I'll need a backtrace of
> the crash in any case.

you don't need it, just create profile and delete it. Simply follow reproducer steps.

NetworkManager-1.0.0-14.git20150121.b4ea599c.el7.x86_64

Created attachment 1025017 [details]
valgrind log

Created attachment 1025035 [details]
valgrtind.log with G_DEBUG=fatal_warnings

editor doesn't open at all for vlan, bridge, team, bond. Just ipsec vpn works.

I was able to reproduce this once but not anymore. Can you still reproduce?

BTW, you can avoid that gdb crash if before you get the stack trace you set this in gdb's prompt:

set auto-load python-scripts off

Created attachment 1029572 [details]
full backtrace

Created attachment 1029595 [details]
new and much shorter backtrace

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://rhn.redhat.com/errata/RHBA-2015-2157.html