Description of problem: First of all, I don't know what caused this problem. The moment I logged into my user account, ABRT popped up and said somthing similar to "gnome-control-center is killed by signal 11". I am dual booting fedora 17 on my mid 2011 macmini. I am using refind for dual boot. I do a "yum update" yesterday. Version-Release number of selected component: control-center-3.4.2-4.fc17 Additional info: libreport version: 2.0.18 abrt_version: 2.0.18 backtrace_rating: 4 cmdline: gnome-control-center network crash_function: net_device_get_nm_device kernel: 3.6.7-4.fc17.x86_64 truncated backtrace: :Thread no. 1 (10 frames) : #0 net_device_get_nm_device at net-device.c:61 : #1 start_hotspot at cc-network-panel.c:3231 : #2 _g_closure_invoke_va at gclosure.c:840 : #5 gtk_real_button_released at gtkbutton.c:2007 : #10 gtk_button_button_release at gtkbutton.c:1842 : #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:6380 : #17 gtk_widget_event at gtkwidget.c:6037 : #18 propagate_event_up at gtkmain.c:2390
Created attachment 651745 [details] File: core_backtrace
Created attachment 651746 [details] File: environ
Created attachment 651747 [details] File: event_log
Created attachment 651748 [details] File: limits
Created attachment 651749 [details] File: backtrace
Created attachment 651750 [details] File: smolt_data
Created attachment 651751 [details] File: cgroup
Created attachment 651752 [details] File: executable
Created attachment 651753 [details] File: maps
Created attachment 651754 [details] File: dso_list
Created attachment 651755 [details] File: proc_pid_status
Created attachment 651756 [details] File: var_log_messages
Created attachment 651757 [details] File: open_fds
This message is a reminder that Fedora 17 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 17. 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 WONTFIX if it remains open with a Fedora 'version' of '17'. 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 prior to Fedora 17's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 17 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 to Fedora 17's end of life. 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 17 changed to end-of-life (EOL) status on 2013-07-30. Fedora 17 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. Thank you for reporting this bug and we are sorry it could not be fixed.