Version-Release number of selected component: evolution-data-server-3.6.2-2.fc18 Additional info: backtrace_rating: 4 cmdline: /usr/libexec/evolution-addressbook-factory crash_function: g_thread_abort executable: /usr/libexec/evolution-addressbook-factory kernel: 3.6.10-4.fc18.x86_64 remote_result: NOTFOUND uid: 1000 var_log_messages: Dec 14 21:47:56 localhost abrt[5654]: Saved core dump of pid 2074 (/usr/libexec/evolution-addressbook-factory) to /var/spool/abrt/ccpp-2012-12-14-21:47:55-2074 (96616448 bytes) Truncated backtrace: Thread no. 1 (10 frames) #2 g_thread_abort at gthread-posix.c:76 #3 g_mutex_unlock at gthread-posix.c:230 #4 g_system_thread_wait at gthread-posix.c:1164 #5 g_thread_join at gthread.c:962 #6 impl_DataBookView_dispose at e-data-book-view.c:725 #7 e_gdbus_marshallers_BOOLEAN__OBJECT at e-gdbus-marshallers.c:124 #12 e_gdbus_stub_handle_method_call at e-gdbus-templates.c:679 #13 call_in_idle_cb at gdbusconnection.c:4737 #18 dbus_server_run_server at e-dbus-server.c:222 #19 ffi_call_unix64 at ../src/x86/unix64.S:75
Thanks for a bug report. ABRT failed to upload full backtrace, unfortunately. Nonetheless, from the truncated backtrace I see that this crashed during the g_thread_join() call, in an addressbook factory, when one of the books was supposed to free its 'view' resources. Could you provide a complete backtrace, with all threads, please? Or even file a new bug report, if it'll happen for you again, and provide some steps what you did before the crash happened, please? Thanks in advance.
I was importing a backup from Fedora 17 backtrace_rating: 4 Package: evolution-data-server-3.6.2-3.fc18 OS Release: Fedora release 18 (Spherical Cow)
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.
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days