Red Hat Bugzilla – Bug 1301389
[abrt] NetworkManager: check_if_startup_complete(): NetworkManager killed by SIGSEGV
Last modified: 2016-11-03 15:06:58 EDT
Version-Release number of selected component:
cmdline: /usr/sbin/NetworkManager --no-daemon
runlevel: N 5
Thread no. 1 (10 frames)
#6 g_object_notify at /lib64/libgobject-2.0.so.0
#11 g_signal_emit_by_name at /lib64/libgobject-2.0.so.0
#14 dispose at /usr/lib64/NetworkManager/libnm-device-plugin-bluetooth.so
#16 g_hash_table_remove_all_nodes at /lib64/libglib-2.0.so.0
#17 g_hash_table_remove_all at /lib64/libglib-2.0.so.0
#18 dispose at /usr/lib64/NetworkManager/libnm-device-plugin-bluetooth.so
Created attachment 1117639 [details]
Created attachment 1117640 [details]
Created attachment 1117641 [details]
Created attachment 1117642 [details]
Created attachment 1117643 [details]
Created attachment 1117644 [details]
Created attachment 1117645 [details]
Created attachment 1117646 [details]
Created attachment 1117647 [details]
Created attachment 1117648 [details]
Created attachment 1117649 [details]
Created attachment 1117650 [details]
Created attachment 1117651 [details]
As far as I can tell my WiFi router was dead at the time and the computer was desperately trying to obtain a DHCP lease when this error happened.
This seems to be the same crash as in bug 1294180.
Yes, it's the same issue as bug 1294180 for Fedora.
The crash is related the bluetooth plugin and happens during regular shutdown of NetworkManager (which makes it slightly lower priority, because NM is anyway about to shut down).
Can we see the backtrace with debug-information installed? Thanks.
(either here or on bug 1294180)
*** Bug 1294180 has been marked as a duplicate of this bug. ***
some fixes for review here: th/bluez-crash-shutdown-rh1301389
but they probably don't tackle the root cause yet...
I didn't experience the duplicate bug with the latest updates. Here's all related packages on my system:
This one happened at a time when my router was dead/dying and I was having problems connecting to it. I'm not even sure how to reproduce nor why ABRT decided that these two are different bugs.
Hmmm, VPN isn't working again. Here's what I did:
1) yum update NetworkManager*
2) everything appeared to be working so I've added comment #20
3) then yum update kernel and everything else
I can't connect to VPN.
5) yum remove NetworkManager-bluetooth && service NetworkManager restart
Still can't connect to VPN. Maybe the duplicate issue is a problem with VPNC after all. ABRT doesn't detect any crashes so I can't get you a traceback with -debugingo installed. The journal isn't of much help as well:
яну 27 13:29:21 aero NetworkManager: <info> VPN plugin state changed: starting (3)
яну 27 13:29:21 aero NetworkManager: <info> VPN connection 'Red Hat Amsterdam' (ConnectInteractive) reply received.
яну 27 13:29:21 aero NetworkManager: <info> VPN plugin state changed: stopped (6)
яну 27 13:29:21 aero NetworkManager: <info> VPN plugin state change reason: unknown (0)
яну 27 13:29:21 aero NetworkManager: ** Message: vpnc started with pid 5777
яну 27 13:29:21 aero NetworkManager: ** Message: Terminated vpnc daemon with PID 5777
(In reply to Alexander Todorov from comment #21)
> I can't connect to VPN.
this BZ and the duped 1294180 contain the backtrace to a crash of NetworkManager while stopping the NetworkManager process and related to the bluetooth plugin.
It would be great if you could provide a stacktrace with debugging symbols installed.
As to the VPN not working, that is unrelated to the crash, please open a different bug.
Preferably attaching a logfile of NetworkManager with DEBUG level enabled (see http://cgit.freedesktop.org/NetworkManager/NetworkManager/tree/contrib/fedora/rpm/NetworkManager.conf?id=bb78d14467c2bb5c85d2efbe84e521148322b1ca#n25 for how to enable it)
the duplicate bug is related to the VPN not working. I don't have NM-bluetooth plugin installed anymore and VPN still fails when I upgrade NM-vpnc. I have no idea why the backtrace isn't related to the VPN plugin but I can consistently reproduce the problem.
Do you want me to re-open bug #1294180 ?
(In reply to Thomas Haller from comment #19)
> some fixes for review here: th/bluez-crash-shutdown-rh1301389
merged as http://cgit.freedesktop.org/NetworkManager/NetworkManager/commit/?id=1a3597529e6389f5b648fe11e95743d41c1fb4b1
There are different issues discussed on this BZ.
(1) For one, there was a crash during shutdown related to bluetooth plugin. That is fixed (comment 4).
(2) Then, there was talking about bug 1294180.
(3) Then, there are some vpnc related issues. This is the main issue, but there isn't enough information in this BZ to investigate that. If the problem still exists, please open a new bug with clean logfiles.
Note that nm-vpnc comes from EPEL, and I remember there were some issues with a nm-vpnc package there. Anyway, please re-test with recent packages and provide the logging information. Thank you.
I interpret this bugzilla as (1) and set the bug to MODIFIED as this is fixed in new rhel-7.3 builds of NetworkManager.
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.