Version-Release number of selected component: control-center-3.16.2-1.fc22 Additional info: reporter: libreport-2.6.2 backtrace_rating: 4 cmdline: gnome-control-center network crash_function: g_type_check_instance_is_a executable: /usr/bin/gnome-control-center global_pid: 7743 kernel: 4.1.5-200.fc22.x86_64 runlevel: N 3 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #0 g_type_check_instance_is_a at gtype.c:4016 #1 gtk_builder_get_object at gtkbuilder.c:1444 #2 device_ethernet_refresh_ui at net-device-ethernet.c:213 #7 connection_inited at nm-remote-settings.c:513 #8 g_simple_async_result_complete at gsimpleasyncresult.c:763 #9 init_async_complete at nm-remote-connection.c:662 #10 init_async_got_properties at nm-remote-connection.c:681 #11 complete_pending_call_and_unlock at dbus-connection.c:2331 #17 g_main_context_iteration at gmain.c:3869 #18 g_application_run at gapplication.c:2308
Created attachment 1065911 [details] File: backtrace
Created attachment 1065912 [details] File: cgroup
Created attachment 1065913 [details] File: core_backtrace
Created attachment 1065914 [details] File: dso_list
Created attachment 1065915 [details] File: environ
Created attachment 1065916 [details] File: limits
Created attachment 1065917 [details] File: maps
Created attachment 1065918 [details] File: mountinfo
Created attachment 1065919 [details] File: namespaces
Created attachment 1065920 [details] File: open_fds
Created attachment 1065921 [details] File: proc_pid_status
Created attachment 1065922 [details] File: var_log_messages
Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.