Bug 1245823

Summary: [abrt] NetworkManager: process_secondaries(): NetworkManager killed by SIGSEGV
Product: [Fedora] Fedora Reporter: Ben Liblit <liblit>
Component: NetworkManagerAssignee: Dan Williams <dcbw>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 22CC: dcbw, jklimes, lkundrak, psimerda
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/805dc0b0fb05859acb75aa5ffad8dc7c63e9b088
Whiteboard: abrt_hash:e7bd5c6896d98f26d31eb790d85639f1dcb4f9c7
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-08-10 16:36:21 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: environ
none
File: limits
none
File: maps
none
File: mountinfo
none
File: namespaces
none
File: open_fds
none
File: proc_pid_status
none
File: var_log_messages none

Description Ben Liblit 2015-07-22 21:06:48 UTC 
Version-Release number of selected component:
NetworkManager-1.0.2-1.fc22

Additional info:
reporter:       libreport-2.6.1
backtrace_rating: 4
cmdline:        /usr/sbin/NetworkManager --no-daemon
crash_function: process_secondaries
executable:     /usr/sbin/NetworkManager
global_pid:     1046
kernel:         4.0.7-300.fc22.x86_64
runlevel:       N 5
type:           CCpp
uid:            0

Truncated backtrace:
Thread no. 1 (6 frames)
 #0 process_secondaries at nm-policy.c:766
 #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:153
 #9 _set_vpn_state at vpn-manager/nm-vpn-connection.c:316
 #10 dispatcher_idle_cb at nm-dispatcher.c:386

Potential duplicate: bug 1175446
Comment 1 Ben Liblit 2015-07-22 21:06:52 UTC 
Created attachment 1055042 [details]
File: backtrace
Comment 2 Ben Liblit 2015-07-22 21:06:53 UTC 
Created attachment 1055043 [details]
File: cgroup
Comment 3 Ben Liblit 2015-07-22 21:06:55 UTC 
Created attachment 1055044 [details]
File: core_backtrace
Comment 4 Ben Liblit 2015-07-22 21:06:56 UTC 
Created attachment 1055045 [details]
File: dso_list
Comment 5 Ben Liblit 2015-07-22 21:06:57 UTC 
Created attachment 1055046 [details]
File: environ
Comment 6 Ben Liblit 2015-07-22 21:06:59 UTC 
Created attachment 1055047 [details]
File: limits
Comment 7 Ben Liblit 2015-07-22 21:07:00 UTC 
Created attachment 1055048 [details]
File: maps
Comment 8 Ben Liblit 2015-07-22 21:07:02 UTC 
Created attachment 1055049 [details]
File: mountinfo
Comment 9 Ben Liblit 2015-07-22 21:07:03 UTC 
Created attachment 1055050 [details]
File: namespaces
Comment 10 Ben Liblit 2015-07-22 21:07:04 UTC 
Created attachment 1055051 [details]
File: open_fds
Comment 11 Ben Liblit 2015-07-22 21:07:05 UTC 
Created attachment 1055052 [details]
File: proc_pid_status
Comment 12 Ben Liblit 2015-07-22 21:07:07 UTC 
Created attachment 1055053 [details]
File: var_log_messages
Comment 13 Jirka Klimes 2015-08-10 16:36:21 UTC 
Do you happen to know how to trigger the bug?

*** This bug has been marked as a duplicate of bug 1175446 ***
Comment 14 Ben Liblit 2015-08-10 16:49:41 UTC 
(In reply to Jirka Klimes from comment #13)
> Do you happen to know how to trigger the bug?

Unfortunately, I do not.