Description of problem: I tried to join the redhat wifi network in brno Version-Release number of selected component: control-center-3.16.2-1.fc22 Additional info: reporter: libreport-2.6.1 backtrace_rating: 4 cmdline: gnome-control-center network crash_function: __strcmp_sse2_unaligned executable: /usr/bin/gnome-control-center global_pid: 19710 kernel: 4.0.8-300.fc22.x86_64 runlevel: N 3 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #0 __strcmp_sse2_unaligned at ../sysdeps/x86_64/multiarch/strcmp-sse2-unaligned.S:29 #1 device_added_cb at net-virtual-device.c:249 #5 g_signal_emit_by_name at gsignal.c:3401 #6 emit_added_removed_signal at nm-object.c:781 #7 object_property_complete at nm-object.c:828 #8 create_async_complete at nm-object.c:598 #9 async_got_type at nm-device.c:971 #10 complete_pending_call_and_unlock at dbus-connection.c:2331 #16 g_main_context_iteration at gmain.c:3869 #17 g_application_run at gapplication.c:2308
Created attachment 1056960 [details] File: backtrace
Created attachment 1056961 [details] File: cgroup
Created attachment 1056962 [details] File: core_backtrace
Created attachment 1056963 [details] File: dso_list
Created attachment 1056964 [details] File: environ
Created attachment 1056965 [details] File: limits
Created attachment 1056966 [details] File: maps
Created attachment 1056967 [details] File: mountinfo
Created attachment 1056968 [details] File: namespaces
Created attachment 1056969 [details] File: open_fds
Created attachment 1056970 [details] File: proc_pid_status
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.