Description of problem: Switched from Mail view to Calendar view. Version-Release number of selected component: evolution-3.4.4-2.fc17 Additional info: libreport version: 2.0.18 abrt_version: 2.0.18 backtrace_rating: 4 cmdline: evolution crash_function: g_object_ref kernel: 3.6.11-1.fc17.x86_64 truncated backtrace: :Thread no. 1 (10 frames) : #0 g_object_ref at gobject.c:2878 : #1 e_cal_client_generate_instances_for_object at e-cal-client.c:2137 : #2 process_added at e-cal-model.c:2377 : #3 process_event at e-cal-model.c:2584 : #4 client_view_objects_added_cb at e-cal-model.c:2628 : #5 g_cclosure_marshal_VOID__POINTERv at gmarshal.c:1236 : #6 _g_closure_invoke_va at gclosure.c:840 : #9 objects_added_cb at e-cal-client-view.c:135 : #15 e_gdbus_proxy_emit_signal at e-gdbus-templates.c:642 : #16 ffi_call_unix64 at ../src/x86/unix64.S:75
Created attachment 679004 [details] File: core_backtrace
Created attachment 679005 [details] File: environ
Created attachment 679006 [details] File: limits
Created attachment 679007 [details] File: backtrace
Created attachment 679008 [details] File: gconf_subtree
Created attachment 679009 [details] File: cgroup
Created attachment 679010 [details] File: smolt_data
Created attachment 679011 [details] File: xsession_errors
Created attachment 679012 [details] File: executable
Created attachment 679013 [details] File: maps
Created attachment 679014 [details] File: dso_list
Created attachment 679015 [details] File: proc_pid_status
Created attachment 679016 [details] File: var_log_messages
Created attachment 679017 [details] File: open_fds
Created attachment 679018 [details] File: build_ids
Thanks for a bug report. I see from the backtrace that the evolution crashed when it tried to add a reference to a GCancellable instance, which is pointing to some garbage probably. This happened when one of your calendars reported event(s) to be shown. I do not see from the code how that could happen, though.
It seems intermittent. After restarting, I didn't get the same crash. I'm planning to upgrade to F18 shortly, so we will see if it happens again after that.
Sounds good, thanks. Please let me know after some usage on Fedora 18. (I'm moving this to need-info). Please note that there will be a 3.6.3 release of evolution packages the next Monday, there might be even more things fixed.
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.