Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

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:
setting some changes to lo device.. autoconnect or so?

Version-Release number of selected component:
nm-connection-editor-0.9.9.0-8.git20131108.el7

Additional info:
reporter:       libreport-2.1.7
backtrace_rating: 4
cmdline:        nm-connection-editor --edit 85308358-55bb-4655-a5c4-eea8fb18dc44
crash_function: remote_call_complete
executable:     /usr/bin/nm-connection-editor
kernel:         3.10.0-48.el7.x86_64
runlevel:       N 5
type:           CCpp
uid:            1000

Truncated backtrace:
Thread no. 1 (3 frames)
 #0 remote_call_complete at nm-remote-connection.c:121
 #1 result_cb at nm-remote-connection.c:145
 #2 complete_pending_call_and_unlock at dbus-connection.c:2314

Created attachment 823879 [details]
File: backtrace

Created attachment 823880 [details]
File: cgroup

Created attachment 823881 [details]
File: core_backtrace

Created attachment 823882 [details]
File: dso_list

Created attachment 823883 [details]
File: environ

Created attachment 823884 [details]
File: exploitable

Created attachment 823885 [details]
File: limits

Created attachment 823886 [details]
File: maps

Created attachment 823887 [details]
File: open_fds

Created attachment 823888 [details]
File: proc_pid_status

Created attachment 823889 [details]
File: var_log_messages

This was caused by a bug in libnm-glib/NetworkManager.

Push a fix to upstream master (or NetworkManager):

http://cgit.freedesktop.org/NetworkManager/NetworkManager/commit/?id=fbcabeb7f72b710a790ca8617f7406a1ba7cf5be

Crashed on removing slave connection from bond

reporter:       libreport-2.1.7
backtrace_rating: 4
cmdline:        nm-connection-editor --edit d8ef0eae-ae5b-4a23-8147-078496033b32
crash_function: remote_call_complete
executable:     /usr/bin/nm-connection-editor
kernel:         3.10.0-55.el7.x86_64
package:        nm-connection-editor-0.9.9.0-8.git20131108.el7
reason:         Process /usr/bin/nm-connection-editor was killed by signal 11 (SIGSEGV)
runlevel:       N 3
type:           CCpp
uid:            1000

cannot manage lo any more

This request was resolved in Red Hat Enterprise Linux 7.0.

Contact your manager or support representative in case you have further questions about the request.