Bug 1299803

Summary: [abrt] NetworkManager: g_type_check_instance_cast(): NetworkManager killed by SIGSEGV
Product: [Fedora] Fedora Reporter: Lubomir Rintel <lkundrak>
Component: NetworkManagerAssignee: Beniamino Galvani <bgalvani>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 23CC: bgalvani, dcbw, lkundrak, psimerda, thaller
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/972e54797e475e978a86f31d79639af424afbfaa
Whiteboard: abrt_hash:1cdd12fc54b026736e6f07fcf690879ecdf09fb1;
Fixed In Version: NetworkManager-1.2.0-0.8.beta3.fc24 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-04-02 15:55:05 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
[PATCH] device/macvlan: implement dispose() none

Description Lubomir Rintel 2016-01-19 10:00:22 UTC 
Description of problem:


Version-Release number of selected component:
NetworkManager-1.1.0-13864.bcd28951a4.fc23

Additional info:
reporter:       libreport-2.6.3
backtrace_rating: 4
cmdline:        /usr/sbin/NetworkManager --no-daemon
crash_function: g_type_check_instance_cast
executable:     /usr/sbin/NetworkManager
global_pid:     4449
kernel:         4.2.8-300.lr1.fc23.x86_64
runlevel:       N 5
type:           CCpp
uid:            0

Truncated backtrace:
Thread no. 1 (4 frames)
 #0 g_type_check_instance_cast at gtype.c:4064
 #1 parent_state_changed at devices/nm-device-macvlan.c:124
 #2 ffi_call_unix64 at ../src/x86/unix64.S:76
 #3 ffi_call at ../src/x86/ffi64.c:525
Comment 1 Lubomir Rintel 2016-01-19 10:00:29 UTC 
Created attachment 1116098 [details]
File: backtrace
Comment 2 Lubomir Rintel 2016-01-19 10:00:30 UTC 
Created attachment 1116099 [details]
File: cgroup
Comment 3 Lubomir Rintel 2016-01-19 10:00:31 UTC 
Created attachment 1116100 [details]
File: core_backtrace
Comment 4 Lubomir Rintel 2016-01-19 10:00:33 UTC 
Created attachment 1116101 [details]
File: dso_list
Comment 5 Lubomir Rintel 2016-01-19 10:00:34 UTC 
Created attachment 1116102 [details]
File: environ
Comment 6 Lubomir Rintel 2016-01-19 10:00:36 UTC 
Created attachment 1116103 [details]
File: limits
Comment 7 Lubomir Rintel 2016-01-19 10:00:37 UTC 
Created attachment 1116104 [details]
File: maps
Comment 8 Lubomir Rintel 2016-01-19 10:00:39 UTC 
Created attachment 1116105 [details]
File: mountinfo
Comment 9 Lubomir Rintel 2016-01-19 10:00:40 UTC 
Created attachment 1116106 [details]
File: namespaces
Comment 10 Lubomir Rintel 2016-01-19 10:00:42 UTC 
Created attachment 1116107 [details]
File: open_fds
Comment 11 Lubomir Rintel 2016-01-19 10:00:43 UTC 
Created attachment 1116108 [details]
File: proc_pid_status
Comment 12 Lubomir Rintel 2016-01-19 10:00:45 UTC 
Created attachment 1116109 [details]
File: var_log_messages
Comment 13 Beniamino Galvani 2016-01-19 13:01:01 UTC 
Created attachment 1116172 [details]
[PATCH] device/macvlan: implement dispose()
Comment 14 Thomas Haller 2016-01-20 09:01:53 UTC 
lgtm.


while at it, can you change:

»···if (priv->parent_state_id)
»···»···nm_clear_g_signal_handler (priv->parent, &priv->parent_state_id);


to simply:

»···nm_clear_g_signal_handler (priv->parent, &priv->parent_state_id);
Comment 15 Beniamino Galvani 2016-01-20 10:52:06 UTC 
(In reply to Thomas Haller from comment #14)
> while at it, can you change:
> to simply:
> 
> »···nm_clear_g_signal_handler (priv->parent, &priv->parent_state_id);

Changed and applied to master:

http://cgit.freedesktop.org/NetworkManager/NetworkManager/commit/?id=f607a16994eab9c587656f5fe2036d51e9eefa67
Comment 16 Mike McCune 2016-03-28 22:20:08 UTC 
This bug was accidentally moved from POST to MODIFIED via an error in automation, please see mmccune with any questions
Comment 17 Fedora Update System 2016-03-29 17:56:40 UTC 
NetworkManager-1.2.0-0.7.beta3.fc24 network-manager-applet-1.2.0-0.3.beta3.fc24 NetworkManager-fortisslvpn-1.2.0-0.4.beta3.fc24 NetworkManager-libreswan-1.2.0-0.4.beta3.fc24 NetworkManager-openconnect-1.2.0-0.3.beta3.fc24 NetworkManager-openvpn-1.2.0-0.3.beta3.fc24 NetworkManager-pptp-1.2.0-0.3.beta3.fc24 NetworkManager-vpnc-1.2.0-0.4.beta3.fc24 has been submitted as an update to Fedora 24. https://bodhi.fedoraproject.org/updates/FEDORA-2016-cd218eef79
Comment 18 Fedora Update System 2016-03-30 22:26:51 UTC 
NetworkManager-1.2.0-0.8.beta3.fc24, NetworkManager-fortisslvpn-1.2.0-0.4.beta3.fc24, NetworkManager-libreswan-1.2.0-0.4.beta3.fc24, NetworkManager-openconnect-1.2.0-0.3.beta3.fc24, NetworkManager-openvpn-1.2.0-0.3.beta3.fc24, NetworkManager-pptp-1.2.0-0.3.beta3.fc24, NetworkManager-strongswan-1.3.1-3.20160330libnm.fc24, NetworkManager-vpnc-1.2.0-0.4.beta3.fc24, network-manager-applet-1.2.0-0.3.beta3.fc24 has been pushed to the Fedora 24 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2016-cd218eef79
Comment 19 Fedora Update System 2016-04-02 15:54:58 UTC 
NetworkManager-1.2.0-0.8.beta3.fc24, NetworkManager-fortisslvpn-1.2.0-0.4.beta3.fc24, NetworkManager-libreswan-1.2.0-0.4.beta3.fc24, NetworkManager-openconnect-1.2.0-0.3.beta3.fc24, NetworkManager-openvpn-1.2.0-0.3.beta3.fc24, NetworkManager-pptp-1.2.0-0.3.beta3.fc24, NetworkManager-strongswan-1.3.1-3.20160330libnm.fc24, NetworkManager-vpnc-1.2.0-0.4.beta3.fc24, network-manager-applet-1.2.0-0.3.beta3.fc24 has been pushed to the Fedora 24 stable repository. If problems still persist, please make note of it in this bug report.