Description of problem: it was consuming CPU. I have two calendars set up which need a password which I never provided. I presume it wants to load calendar entries but fails due to the missing password. I killed it by hand because I didn't know how to stop it from burning my CPU. Version-Release number of selected component: evolution-3.6.4-3.fc18 Additional info: backtrace_rating: 4 cmdline: /usr/libexec/evolution/3.6/evolution-alarm-notify crash_function: handler_lookup executable: /usr/libexec/evolution/3.6/evolution-alarm-notify kernel: 3.8.9-200.fc18.x86_64 smolt_data: Unable to save UUID to /etc/smolt/hw-uuid. Please run once as root. uid: 1000 ureports_counter: 1 var_log_messages: May 15 12:55:36 bigbox abrt[27446]: Saved core dump of pid 1386 (/usr/libexec/evolution/3.6/evolution-alarm-notify) to /var/tmp/abrt/ccpp-2013-05-15-12:55:29-1386 (150208512 bytes) Truncated backtrace: Thread no. 1 (10 frames) #0 handler_lookup at gsignal.c:439 #1 g_signal_handler_disconnect at gsignal.c:2568 #2 signal_handlers_foreach_matched_R at gsignal.c:2719 #3 g_signal_handlers_disconnect_matched at gsignal.c:2862 #4 free_client_utils_async_op_data at e-client-utils.c:101 #5 client_utils_open_new_async_cb at e-client-utils.c:315 #6 g_simple_async_result_complete at gsimpleasyncresult.c:775 #7 finish_async_op at e-client.c:2003 #8 async_result_ready_cb at e-client.c:2040 #9 g_simple_async_result_complete at gsimpleasyncresult.c:775
Created attachment 748262 [details] File: backtrace
Created attachment 748263 [details] File: cgroup
Created attachment 748264 [details] File: core_backtrace
Created attachment 748265 [details] File: dso_list
Created attachment 748266 [details] File: environ
Created attachment 748267 [details] File: limits
Created attachment 748268 [details] File: maps
Created attachment 748269 [details] File: open_fds
Created attachment 748270 [details] File: proc_pid_status
Created attachment 748271 [details] File: xsession_errors
Thanks for a bug report. I guess this is related to bug #953641, could you verify your gcr version, and follow steps from that bug report if the version you have is the broken one, please?
Hm. I don't feel this is relevant. I've commented in the other bug. Note that nothing knows the password for the calendars that I've set up. It's especially not saved in the keyring. I described it a little in bug 959628.
This message is a reminder that Fedora 18 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 18. 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 '18'. 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 18's end of life. Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 18 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 18'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 18 changed to end-of-life (EOL) status on 2014-01-14. Fedora 18 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.