Version-Release number of selected component: control-center-3.8.3-2.fc19 Additional info: reporter: libreport-2.1.5 backtrace_rating: 4 cmdline: gnome-control-center network crash_function: net_connection_editor_set_connection executable: /usr/bin/gnome-control-center kernel: 3.9.8-300.fc19.x86_64 runlevel: 3 5 uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #0 net_connection_editor_set_connection at net-connection-editor.c:526 #1 net_connection_editor_new at net-connection-editor.c:926 #2 show_details_for_row at net-device-wifi.c:1682 #3 _g_closure_invoke_va at gclosure.c:840 #6 gtk_real_button_released at gtkbutton.c:1967 #11 gtk_button_button_release at gtkbutton.c:1802 #12 _gtk_marshal_BOOLEAN__BOXEDv at gtkmarshalers.c:130 #13 _g_closure_invoke_va at gclosure.c:840 #16 gtk_widget_event_internal at gtkwidget.c:6714 #17 gtk_widget_event at gtkwidget.c:6371
Created attachment 769887 [details] File: backtrace
Created attachment 769888 [details] File: cgroup
Created attachment 769889 [details] File: core_backtrace
Created attachment 769890 [details] File: dso_list
Created attachment 769891 [details] File: environ
Created attachment 769892 [details] File: limits
Created attachment 769893 [details] File: maps
Created attachment 769894 [details] File: open_fds
Created attachment 769895 [details] File: proc_pid_status
Created attachment 769896 [details] File: var_log_messages
Yesterday I used the "Forget" option to forget the settings for a WPA2-PSK network. The description on this option is "Remove all details relating to this network and do not try to automatically connect." Today, I noticed that NetworkManager had reconnected to this network, which would be impossible had it indeed removed the network password. I'm extremely concerned that this was not performed correctly. I clicked on the "Forget" button to try again and was returned to the main Network tab, but the network still had a gear menu suggesting the presence of settings. When I clicked on this menu, control-center crashed. reporter: libreport-2.1.5 backtrace_rating: 4 cmdline: gnome-control-center network crash_function: net_connection_editor_set_connection executable: /usr/bin/gnome-control-center kernel: 3.9.9-302.fc19.x86_64 package: control-center-3.8.3-2.fc19 reason: Process /usr/bin/gnome-control-center was killed by signal 11 (SIGSEGV) runlevel: N 5 uid: 1000
Same problem here. Right after clicking on the forget button, the "gear button" to configure the forgotten network was still there, and clicking it will make network manager crash. Steps to reproduce: 1) Forget one network. 2) Click on the configuration button of the forgotten network, which is still there right after forgetting it.
Was editing a wireless connecting, pushed the "forget" button, but the connection remained in the list, then I pressed the setting/options button on it again, and it crashed. When I started it up again, the network had been removed. reporter: libreport-2.1.5 backtrace_rating: 4 cmdline: gnome-control-center network crash_function: net_connection_editor_set_connection executable: /usr/bin/gnome-control-center kernel: 3.9.9-302.fc19.x86_64 package: control-center-3.8.3-2.fc19 reason: Process /usr/bin/gnome-control-center was killed by signal 11 (SIGSEGV) runlevel: N 5 uid: 1236200002 xsession_errors:
same problem as described in comment 12
*** Bug 1016156 has been marked as a duplicate of this bug. ***
Same symptoms.
This message is a notice that Fedora 19 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 19. It is Fedora's policy to close all bug reports from releases that are no longer maintained. Approximately 4 (four) weeks from now this bug will be closed as EOL if it remains open with a Fedora 'version' of '19'. 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 19 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 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 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.