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 1589724 - [abrt] [faf] NetworkManager: _g_log_abort(): /usr/sbin/NetworkManager killed by 5
Summary: [abrt] [faf] NetworkManager: _g_log_abort(): /usr/sbin/NetworkManager killed ...
Keywords:
Status: CLOSED DUPLICATE of bug 1543871
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: NetworkManager
Version: 7.5
Hardware: x86_64
OS: Linux
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: sushil kulkarni
QA Contact: Desktop QE
URL: http://faf.lab.eng.brq.redhat.com/faf...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-06-11 09:21 UTC by Tomas Hudziec
Modified: 2018-06-11 09:47 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-06-11 09:47:04 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Tomas Hudziec 2018-06-11 09:21:25 UTC
This bug has been created based on an anonymous crash report requested by the package maintainer.

Report URL: http://faf.lab.eng.brq.redhat.com/faf/reports/bthash/6c0b014f06ede051be17865fa3befeb4baf8ddd9/

Comment 2 Beniamino Galvani 2018-06-11 09:47:04 UTC
1 _g_log_abort 	/usr/lib64/libglib-2.0.so.0.5400.2 	0x50381
2 g_logv 	/usr/lib64/libglib-2.0.so.0.5400.2 	0x516a2
3 g_log 	/usr/lib64/libglib-2.0.so.0.5400.2 	0x5180f
4 _nm_g_return_if_fail_warning.constprop.0 	/usr/sbin/NetworkManager 	0x35195
5 nm_device_factory_manager_find_factory_for_connection 	/usr/sbin/NetworkManager 	0x14a97a
6 nm_manager_get_connection_iface 	/usr/sbin/NetworkManager 	0x5d6a8
7 check_connection_compatible 	/usr/sbin/NetworkManager 	0x123c13
8 check_connection_compatible 	/usr/lib64/NetworkManager/libnm-device-plugin-ovs.so 	0x8d41
9 nm_device_check_connection_available 	/usr/sbin/NetworkManager 	0x136700
10 nm_device_recheck_available_connections 	/usr/sbin/NetworkManager 	0x136a90
11 _set_state_full 	/usr/sbin/NetworkManager 	0x13a588
12 del_iface_cb 	/usr/lib64/NetworkManager/libnm-device-plugin-ovs.so 	0x910d
13 _transact_cb 	/usr/lib64/NetworkManager/libnm-device-plugin-ovs.so 	0x5c65
14 ovsdb_disconnect 	/usr/lib64/NetworkManager/libnm-device-plugin-ovs.so 	0x4ac3
15 dispose 	/usr/lib64/NetworkManager/libnm-device-plugin-ovs.so 	0x6339
16 g_object_unref 	/usr/lib64/libgobject-2.0.so.0.5400.2 	0x14962
17 _nm_singleton_instance_destroy 	/usr/sbin/NetworkManager 	0x37865
18 _dl_fini 	/usr/lib64/ld-2.17.so 	0x1018a
19 __run_exit_handlers 	/usr/lib64/libc-2.17.so 	0x39b69
20 	/usr/lib64/libc-2.17.so 	0x39bb7
21 main 	/usr/sbin/NetworkManager 	0x37f3a

*** This bug has been marked as a duplicate of bug 1543871 ***


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