Description of problem: I'm sorry, I do not know It was too long ago to remember - perhaps abrt should request information immediately? Version-Release number of selected component: control-center-3.10.3-1.fc20 Additional info: reporter: libreport-2.2.2 backtrace_rating: 4 cmdline: gnome-control-center network show-device /org/freedesktop/NetworkManager/Devices/2 crash_function: utils_update_password_storage executable: /usr/bin/gnome-control-center kernel: 3.13.9-200.fc20.x86_64 runlevel: N 5 type: CCpp uid: 1001 Truncated backtrace: Thread no. 1 (10 frames) #0 utils_update_password_storage at utils.c:449 #1 fill_connection at ws-wpa-psk.c:133 #2 nma_wifi_dialog_get_connection at nm-wifi-dialog.c:1228 #3 wireless_dialog_response_cb at network-dialogs.c:152 #8 _g_closure_invoke_va at gclosure.c:840 #11 gtk_real_button_released at gtkbutton.c:2106 #16 gtk_button_button_release at gtkbutton.c:1938 #17 _gtk_marshal_BOOLEAN__BOXEDv at gtkmarshalers.c:130 #18 _g_closure_invoke_va at gclosure.c:840 #21 gtk_widget_event_internal at gtkwidget.c:7168
Created attachment 895062 [details] File: backtrace
Created attachment 895063 [details] File: cgroup
Created attachment 895064 [details] File: core_backtrace
Created attachment 895065 [details] File: dso_list
Created attachment 895066 [details] File: environ
Created attachment 895067 [details] File: exploitable
Created attachment 895068 [details] File: limits
Created attachment 895069 [details] File: maps
Created attachment 895070 [details] File: open_fds
Created attachment 895071 [details] File: proc_pid_status
Created attachment 895072 [details] File: var_log_messages
Another user experienced a similar problem: gnome-control-center crashes (segmentation fault, as reported in STDIN when run in command-line) when I try to connect to a new hidden wifi network with WPA2 security. It does not crash if I enter a bogus WPA2 password, just with the correct one. It does not crash either when I try using any other security protocol or none at all, but then again only correct settings seem to trigger the segfault, so I don't know if that information is useful. I'm running Fedora 20 with Openbox. Kernel: 3.14.4-200.fc20.x86_64 control-center version: 3.10.3 (rev. 1.fc20) Did I miss anything? I know that chances are it's a duplicate but bugzilla.redhat.com is so sluggish here I can't get any search result, so I'm shooting in the dark here. Sorry 'bout that. Here is the full output (some of it in french, but it should be straightforward): [prompt]$ gnome-control-center (gnome-control-center:11328): IBUS-WARNING **: Unable to connect to ibus: Impossible de se connecter : Connexion refusée (gnome-control-center:11328): GLib-CRITICAL **: g_variant_get_type: assertion 'value != NULL' failed (gnome-control-center:11328): GLib-CRITICAL **: g_variant_type_is_subtype_of: assertion 'g_variant_type_check (type)' failed (gnome-control-center:11328): GLib-CRITICAL **: g_variant_get_boolean: assertion 'g_variant_is_of_type (value, G_VARIANT_TYPE_BOOLEAN)' failed ** (gnome-control-center:11328): CRITICAL **: nm_connection_get_setting_by_name: assertion 'NM_IS_CONNECTION (connection)' failed ** (gnome-control-center:11328): CRITICAL **: nm_connection_get_setting_by_name: assertion 'NM_IS_CONNECTION (connection)' failed ** (gnome-control-center:11328): CRITICAL **: nm_connection_get_setting_by_name: assertion 'NM_IS_CONNECTION (connection)' failed ** (gnome-control-center:11328): CRITICAL **: nm_connection_get_setting_by_name: assertion 'NM_IS_CONNECTION (connection)' failed ** (gnome-control-center:11328): CRITICAL **: nm_connection_get_setting_by_name: assertion 'NM_IS_CONNECTION (connection)' failed ** (gnome-control-center:11328): CRITICAL **: nm_connection_get_setting_by_name: assertion 'NM_IS_CONNECTION (connection)' failed ** (gnome-control-center:11328): CRITICAL **: nm_connection_get_setting_by_name: assertion 'NM_IS_CONNECTION (connection)' failed ** (gnome-control-center:11328): CRITICAL **: nm_connection_get_setting_by_name: assertion 'NM_IS_CONNECTION (connection)' failed ** (gnome-control-center:11328): CRITICAL **: nm_connection_get_setting_by_name: assertion 'NM_IS_CONNECTION (connection)' failed ** (gnome-control-center:11328): CRITICAL **: nm_connection_get_setting_by_name: assertion 'NM_IS_CONNECTION (connection)' failed ** (gnome-control-center:11328): CRITICAL **: nm_connection_get_setting_by_name: assertion 'NM_IS_CONNECTION (connection)' failed ** (gnome-control-center:11328): CRITICAL **: nm_connection_get_setting_by_name: assertion 'NM_IS_CONNECTION (connection)' failed ** (gnome-control-center:11328): CRITICAL **: nm_connection_get_setting_by_name: assertion 'NM_IS_CONNECTION (connection)' failed ** (gnome-control-center:11328): CRITICAL **: nm_connection_get_setting_by_name: assertion 'NM_IS_CONNECTION (connection)' failed ** (gnome-control-center:11328): CRITICAL **: nm_connection_get_setting_by_name: assertion 'NM_IS_CONNECTION (connection)' failed ** (gnome-control-center:11328): CRITICAL **: nm_connection_get_setting_by_name: assertion 'NM_IS_CONNECTION (connection)' failed ** (gnome-control-center:11328): CRITICAL **: nm_connection_get_setting_by_name: assertion 'NM_IS_CONNECTION (connection)' failed ** (gnome-control-center:11328): CRITICAL **: nm_connection_get_setting_by_name: assertion 'NM_IS_CONNECTION (connection)' failed ** (gnome-control-center:11328): CRITICAL **: nm_connection_get_setting_by_name: assertion 'NM_IS_CONNECTION (connection)' failed ** (gnome-control-center:11328): CRITICAL **: nm_connection_get_setting_by_name: assertion 'NM_IS_CONNECTION (connection)' failed ** (gnome-control-center:11328): CRITICAL **: nm_connection_get_setting_by_name: assertion 'NM_IS_CONNECTION (connection)' failed ** (gnome-control-center:11328): CRITICAL **: nm_connection_get_setting_by_name: assertion 'NM_IS_CONNECTION (connection)' failed ** (gnome-control-center:11328): CRITICAL **: nm_connection_get_setting_by_name: assertion 'NM_IS_CONNECTION (connection)' failed ** (gnome-control-center:11328): CRITICAL **: nm_connection_get_setting_by_name: assertion 'NM_IS_CONNECTION (connection)' failed ** (gnome-control-center:11328): CRITICAL **: nm_connection_get_setting_by_name: assertion 'NM_IS_CONNECTION (connection)' failed ** (gnome-control-center:11328): CRITICAL **: nm_connection_get_setting_by_name: assertion 'NM_IS_CONNECTION (connection)' failed ** (gnome-control-center:11328): CRITICAL **: nm_connection_get_setting_by_name: assertion 'NM_IS_CONNECTION (connection)' failed ** (gnome-control-center:11328): CRITICAL **: nm_connection_get_setting_by_name: assertion 'NM_IS_CONNECTION (connection)' failed (gnome-control-center:11328): Gtk-CRITICAL **: gtk_radio_menu_item_get_group: assertion 'GTK_IS_RADIO_MENU_ITEM (radio_menu_item)' failed Erreur de segmentation (core dumped) reporter: libreport-2.2.2 backtrace_rating: 4 cmdline: gnome-control-center network crash_function: utils_update_password_storage executable: /usr/bin/gnome-control-center kernel: 3.14.3-200.fc20.x86_64 package: control-center-3.10.3-1.fc20 reason: gnome-control-center killed by SIGSEGV runlevel: N 5 type: CCpp uid: 1000
I confirm segfaults in gnome-control-center on adding new password-protected WiFi configurations. I worked around it by typing the wrong settings, saving it, and then editing the settings with the right password. Name : NetworkManager Epoch : 1 Version : 0.9.9.0 Release : 41.git20131003.fc20 Architecture: x86_64 Name : control-center Epoch : 1 Version : 3.10.3 Release : 1.fc20 Architecture: x86_64 Install Date: Thu 13 Mar 2014 09:15:47 SAST PS. For me this started when I deleted all settings and started again. I did that, because wake-from-suspend made NetworkManager start a Hotspot -- and thus stop connecting.
This message is a reminder that Fedora 20 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 20. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '20'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 20 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 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.