Bug 1175446

Summary: [abrt] NetworkManager: process_secondaries(): NetworkManager killed by SIGSEGV
Product: [Fedora] Fedora Reporter: Minus Zero <minuszero>
Component: NetworkManagerAssignee: Lubomir Rintel <lkundrak>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 21CC: dcbw, dgunchev, eliadevito, fredrik, godlike_devil, jklimes, liblit, mehul.sanghvi, minuszero, neil, paul.may9115, psimerda, vlad
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/1a3380aa6944e4699d37e00b7e4d25fc01eeaa7e
Whiteboard: abrt_hash:e7bd5c6896d98f26d31eb790d85639f1dcb4f9c7
Fixed In Version: NetworkManager-1.0.6-8.fc23 NetworkManager-1.0.6-8.fc22 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-11-08 06:50:25 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
File: backtrace
none
File: cgroup
none
File: core_backtrace
none
File: dso_list
none
File: exploitable
none
File: limits
none
File: maps
none
File: open_fds
none
File: proc_pid_status
none
File: var_log_messages none

Description Minus Zero 2014-12-17 18:31:17 UTC
Description of problem:
I was enabling and disabling the wifi from the nm-applet option.

Version-Release number of selected component:
NetworkManager-0.9.10.0-14.git20140704.fc21

Additional info:
reporter:       libreport-2.3.0
backtrace_rating: 4
cmdline:        /usr/sbin/NetworkManager --no-daemon
crash_function: process_secondaries
executable:     /usr/sbin/NetworkManager
kernel:         3.17.6-300.fc21.x86_64
runlevel:       N 5
type:           CCpp
uid:            0

Truncated backtrace:
Thread no. 1 (6 frames)
 #0 process_secondaries at nm-policy.c:1100
 #6 g_object_notify_by_spec_internal at gobject.c:1149
 #7 g_object_notify at gobject.c:1197
 #8 nm_active_connection_set_state at nm-active-connection.c:140
 #9 _set_vpn_state at vpn-manager/nm-vpn-connection.c:311
 #10 dispatcher_idle_cb at nm-dispatcher.c:380

Comment 1 Minus Zero 2014-12-17 18:31:22 UTC
Created attachment 970274 [details]
File: backtrace

Comment 2 Minus Zero 2014-12-17 18:31:23 UTC
Created attachment 970275 [details]
File: cgroup

Comment 3 Minus Zero 2014-12-17 18:31:25 UTC
Created attachment 970276 [details]
File: core_backtrace

Comment 4 Minus Zero 2014-12-17 18:31:27 UTC
Created attachment 970277 [details]
File: dso_list

Comment 5 Minus Zero 2014-12-17 18:31:30 UTC
Created attachment 970278 [details]
File: exploitable

Comment 6 Minus Zero 2014-12-17 18:31:31 UTC
Created attachment 970279 [details]
File: limits

Comment 7 Minus Zero 2014-12-17 18:31:34 UTC
Created attachment 970280 [details]
File: maps

Comment 8 Minus Zero 2014-12-17 18:31:35 UTC
Created attachment 970281 [details]
File: open_fds

Comment 9 Minus Zero 2014-12-17 18:31:37 UTC
Created attachment 970282 [details]
File: proc_pid_status

Comment 10 Minus Zero 2014-12-17 18:31:39 UTC
Created attachment 970283 [details]
File: var_log_messages

Comment 11 fredrik@mikker.se 2015-01-24 03:48:07 UTC
This issue also happens when a VPN is configured to autoconnect when connecting to a WiFi.

Comment 12 fredrik@mikker.se 2015-01-27 02:39:10 UTC
For reference: https://bugzilla.redhat.com/show_bug.cgi?id=483120

Comment 13 Dan Williams 2015-01-29 19:36:09 UTC
Are you able to reproduce this issue reliably?  I just tried with 0.9.10 and a "secondary" VPN and couldn't, while toggling the WiFi switch on and off quite a few times.

Comment 14 Jirka Klimes 2015-05-04 10:25:17 UTC
*** Bug 1209620 has been marked as a duplicate of this bug. ***

Comment 15 neil 2015-05-15 01:01:00 UTC
This happens on my desktop (Wired LAN) when resuming from suspend-to-ram.
Also on my laptop (WiFi) when resuming from hibernate. 
Doesn't happen every time, but several times per week.

Both are FC21 and have an openvpn connection configured to autoconnect.

Comment 16 Jirka Klimes 2015-08-10 16:36:21 UTC
*** Bug 1245823 has been marked as a duplicate of this bug. ***

Comment 17 Fedora Admin XMLRPC Client 2015-08-18 14:58:10 UTC
This package has changed ownership in the Fedora Package Database.  Reassigning to the new owner of this component.

Comment 18 Fedora End Of Life 2015-11-04 10:13:51 UTC
This message is a reminder that Fedora 21 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 21. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '21'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 21 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 19 Jirka Klimes 2015-11-04 15:50:50 UTC
I have managed to identify the problem. (While debugging on a test machine I was able to hit it sometimes).
The problem was in traversing a list while removing elements.

Fix is available in upstream branch jk/vpn-secondaries-fix-rh1175446.

Comment 20 Jirka Klimes 2015-11-05 12:01:45 UTC
The fix committed upstream:
master: b9da3d9 policy: fix looping through list while removing elements (rh #1175446)
nm-1-0: 112f3f8 policy: fix looping through list while removing elements (rh #1175446)

Comment 21 Fedora Update System 2015-11-05 16:27:32 UTC
NetworkManager-1.0.6-8.fc22 has been submitted as an update to Fedora 22. https://bodhi.fedoraproject.org/updates/FEDORA-2015-38fc6652a8

Comment 22 Fedora Update System 2015-11-05 16:27:32 UTC
NetworkManager-1.0.6-8.fc23 has been submitted as an update to Fedora 23. https://bodhi.fedoraproject.org/updates/FEDORA-2015-bbc8935459

Comment 23 Fedora Update System 2015-11-06 00:50:43 UTC
NetworkManager-1.0.6-8.fc22 has been pushed to the Fedora 22 testing repository. If problems still persist, please make note of it in this bug report.
If you want to test the update, you can install it with
$ su -c 'dnf --enablerepo=updates-testing update NetworkManager'
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2015-38fc6652a8

Comment 24 Fedora Update System 2015-11-06 02:34:00 UTC
NetworkManager-1.0.6-8.fc23 has been pushed to the Fedora 23 testing repository. If problems still persist, please make note of it in this bug report.
If you want to test the update, you can install it with
$ su -c 'dnf --enablerepo=updates-testing update NetworkManager'
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2015-bbc8935459

Comment 25 Fedora Update System 2015-11-08 06:50:11 UTC
NetworkManager-1.0.6-8.fc23 has been pushed to the Fedora 23 stable repository. If problems still persist, please make note of it in this bug report.

Comment 26 Fedora Update System 2015-11-17 18:23:01 UTC
NetworkManager-1.0.6-8.fc22 has been pushed to the Fedora 22 stable repository. If problems still persist, please make note of it in this bug report.