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:
when Network c-c is open and NM service restarted c-c crashes.

see attached bt

Version-Release number of selected component (if applicable):
control-center-3.14.5-8.el7.x86_64
NetworkManager-1.0.6-27.el7.x86_64


How reproducible:
always

Steps to Reproduce:
1.go into control-center
2.restart NM service

Actual results:
crash

Expected results:
no crash

Additional info:

Created attachment 1121060 [details]
bt

I can't think of any use cases where we'd want to NetworkManager to be restarted from under a graphical session.

A rebased GNOME in a future version of RHEL would automatically get a number of fixes in that area, but given how the problem is reproduced, I'm happy to let it happen again.

Development Management has reviewed and declined this request.
You may appeal this decision by reopening this request.