Version-Release number of selected component: NetworkManager-1.0.4-0.1.git20160624.f245b49a.fc22 Additional info: reporter: libreport-2.6.0 backtrace_rating: 4 cmdline: /usr/sbin/NetworkManager --no-daemon crash_function: nm_supplicant_interface_get_scanning executable: /usr/sbin/NetworkManager global_pid: 934 kernel: 4.2.0-0.rc1.git0.1.fc23.x86_64 runlevel: N 5 type: CCpp uid: 0 Truncated backtrace: Thread no. 1 (8 frames) #0 nm_supplicant_interface_get_scanning at supplicant-manager/nm-supplicant-interface.c:316 #1 scanning_allowed at nm-device-wifi.c:1368 #2 ffi_call_unix64 at ../src/x86/unix64.S:76 #3 ffi_call at ../src/x86/ffi64.c:525 #4 g_cclosure_marshal_generic at gclosure.c:1448 #7 g_signal_emitv at gsignal.c:3044 #8 check_scanning_allowed at nm-device-wifi.c:1420 #9 request_wireless_scan at nm-device-wifi.c:1498
Created attachment 1049929 [details] File: backtrace
Created attachment 1049930 [details] File: cgroup
Created attachment 1049931 [details] File: core_backtrace
Created attachment 1049932 [details] File: dso_list
Created attachment 1049933 [details] File: environ
Created attachment 1049934 [details] File: limits
Created attachment 1049935 [details] File: maps
Created attachment 1049936 [details] File: mountinfo
Created attachment 1049937 [details] File: namespaces
Created attachment 1049938 [details] File: open_fds
Created attachment 1049939 [details] File: proc_pid_status
Created attachment 1049940 [details] File: var_log_messages
#0 nm_supplicant_interface_get_scanning (self=0x55dfbf30a2d0) at supplicant-manager/nm-supplicant-interface.c:316 priv = 0x0 __FUNCTION__ = "nm_supplicant_interface_get_scanning" priv is NULL, so the NMSupplicantInterface must be invalid. Hmm, but just before nm_supplicant_interface_get_state() passed with the same object. Chris, any idea how to trigger the bug?
No. Many different things were all happening at this time and I'm not even sure at what point the crash happened, but then saw the notification so I filed the bug.
This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component.
Might be related to bug 1298007 as that fixed possible invalid reference counting in the supplicant code.
(In reply to Dan Williams from comment #16) > Might be related to bug 1298007 as that fixed possible invalid reference > counting in the supplicant code. bug 1298007 happens when the wifi device gets renamed. The information on this bug isn't sufficient to determine whether that was the case. However, it might well be. please read https://bugzilla.redhat.com/show_bug.cgi?id=1298007#c19 https://bugzilla.redhat.com/show_bug.cgi?id=1298007#c20 With NetworkManager-1.0.10-3.fc22, the crash should be avoided. If it still happens, we know it's a different issue.
NetworkManager-1.0.12-1.fc23 has been pushed to the Fedora 23 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-8201e3fefa
NetworkManager-1.0.12-1.fc23 has been pushed to the Fedora 23 stable repository. If problems still persist, please make note of it in this bug report.