Description of problem: Wireless driver stopped working so I unloaded and reloaded it. Version-Release number of selected component: NetworkManager-0.9.8.2-8.git20130709.fc19 Additional info: reporter: libreport-2.1.5 backtrace_rating: 4 cmdline: /usr/sbin/NetworkManager --no-daemon crash_function: nm_active_connection_get_path executable: /usr/sbin/NetworkManager kernel: 3.9.8-300.fc19.x86_64 runlevel: N 5 uid: 0 Truncated backtrace: Thread no. 1 (7 frames) #0 nm_active_connection_get_path at nm-active-connection.c:142 #1 get_property at nm-manager.c:4466 #2 object_get_property at gobject.c:1295 #3 g_object_get_property at gobject.c:2229 #4 get_all_object_properties at dbus-gobject.c:1322 #5 object_registration_message at dbus-gobject.c:2204 #6 _dbus_object_tree_dispatch_and_unlock at dbus-object-tree.c:862 Potential duplicate: bug 946920
Created attachment 775001 [details] File: backtrace
Created attachment 775002 [details] File: cgroup
Created attachment 775003 [details] File: core_backtrace
Created attachment 775004 [details] File: dso_list
Created attachment 775005 [details] File: environ
Created attachment 775006 [details] File: limits
Created attachment 775007 [details] File: maps
Created attachment 775008 [details] File: open_fds
Created attachment 775009 [details] File: proc_pid_status
Created attachment 775010 [details] File: var_log_messages
bridge setting crashed reporter: libreport-2.1.5 backtrace_rating: 4 cmdline: /usr/sbin/NetworkManager --no-daemon crash_function: nm_active_connection_get_path executable: /usr/sbin/NetworkManager kernel: 3.9.9-302.fc19.x86_64 package: NetworkManager-0.9.8.2-8.git20130709.fc19 reason: Process /usr/sbin/NetworkManager was killed by signal 11 (SIGSEGV) runlevel: 3 5 uid: 0
case PROP_ACTIVE_CONNECTIONS: active = g_ptr_array_sized_new (3); for (iter = priv->active_connections; iter; iter = g_slist_next (iter)) { ---> path = nm_active_connection_get_path (NM_ACTIVE_CONNECTION (iter->data)); g_ptr_array_add (active, g_strdup (path)); } g_value_take_boxed (value, active); break; The active connection has to be freed before. Probably, due to removing a device. Yeah, it is duplicate of bug 946920. David, are you able to reproduce? *** This bug has been marked as a duplicate of bug 946920 ***