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
Created attachment 1055042 [details] File: backtrace
Created attachment 1055043 [details] File: cgroup
Created attachment 1055044 [details] File: core_backtrace
Created attachment 1055045 [details] File: dso_list
Created attachment 1055046 [details] File: environ
Created attachment 1055047 [details] File: limits
Created attachment 1055048 [details] File: maps
Created attachment 1055049 [details] File: mountinfo
Created attachment 1055050 [details] File: namespaces
Created attachment 1055051 [details] File: open_fds
Created attachment 1055052 [details] File: proc_pid_status
Created attachment 1055053 [details] File: var_log_messages
Do you happen to know how to trigger the bug? *** This bug has been marked as a duplicate of bug 1175446 ***
(In reply to Jirka Klimes from comment #13) > Do you happen to know how to trigger the bug? Unfortunately, I do not.