I think the tracker plugin might be teh suck. #0 0x00447422 in __kernel_vsyscall () #1 0x00998f6b in read () from /lib/libpthread.so.0 #2 0x030132e1 in ?? () from /usr/lib/libsqlite3.so.0 #3 0x00d9bb06 in ?? () from /usr/lib/libcamel-1.2.so.14 #4 0x02ffd19d in ?? () from /usr/lib/libsqlite3.so.0 #5 0x030240bf in ?? () from /usr/lib/libsqlite3.so.0 #6 0x03024254 in ?? () from /usr/lib/libsqlite3.so.0 #7 0x03025172 in ?? () from /usr/lib/libsqlite3.so.0 #8 0x030251bb in ?? () from /usr/lib/libsqlite3.so.0 #9 0x03025304 in ?? () from /usr/lib/libsqlite3.so.0 #10 0x03064650 in ?? () from /usr/lib/libsqlite3.so.0 #11 0x0304ec4f in sqlite3_step () from /usr/lib/libsqlite3.so.0 #12 0x03052a5a in sqlite3_exec () from /usr/lib/libsqlite3.so.0 #13 0x00d98716 in camel_db_select () from /usr/lib/libcamel-1.2.so.14 #14 0x00d98e85 in camel_db_get_folder_uids_flags () from /usr/lib/libcamel-1.2.so.14 #15 0x001b32c6 in camel_folder_summary_load_from_db () from /usr/lib/libcamel-provider-1.2.so.14 #16 0x05c3ad68 in camel_imap_summary_new () from /usr/lib/evolution-data-server-1.2/camel-providers/libcamelimap.so #17 0x05c2a5b0 in camel_imap_folder_new () from /usr/lib/evolution-data-server-1.2/camel-providers/libcamelimap.so #18 0x05c38c04 in ?? () from /usr/lib/evolution-data-server-1.2/camel-providers/libcamelimap.so #19 0x001d5968 in camel_store_get_folder () from /usr/lib/libcamel-provider-1.2.so.14 #20 0x0867470a in ?? () from /usr/lib/evolution/2.26/plugins/liborg-freedesktop-Tracker-evolution-plugin.so #21 0x08674a22 in ?? () from /usr/lib/evolution/2.26/plugins/liborg-freedesktop-Tracker-evolution-plugin.so #22 0x03ccd73e in ?? () from /usr/lib/evolution/2.26/components/libevolution-mail.so #23 0x03cca4e6 in ?? () from /usr/lib/evolution/2.26/components/libevolution-mail.so #24 0x00b72341 in g_idle_dispatch (source=0xb5a00d30, callback=0x400, user_data=0x0) at gmain.c:3922 #25 0x00b741e8 in g_main_dispatch (context=<value optimized out>) at gmain.c:1814 #26 IA__g_main_context_dispatch (context=<value optimized out>) at gmain.c:2367 #27 0x00b777f8 in g_main_context_iterate (context=0x8c5d9c8, block=<value optimized out>, dispatch=1, self=0x8c30860) at gmain.c:2448 #28 0x00b77caf in IA__g_main_loop_run (loop=0x919c648) at gmain.c:2656 #29 0x01033ec1 in IA__gtk_dialog_run (dialog=0x8cffcd0) at gtkdialog.c:1090 #30 0x002c7534 in e_error_run () from /usr/lib/evolution/2.26/libeutil.so.0 #31 0x03cf285d in e_msg_composer_check_autosave () from /usr/lib/evolution/2.26/components/libevolution-mail.so #32 0x03cc1b3e in ?? () from /usr/lib/evolution/2.26/components/libevolution-mail.so #33 0x00b7490c in g_timeout_dispatch (source=0x908a128, callback=0x400, user_data=0x0) at gmain.c:3253 #34 0x00b741e8 in g_main_dispatch (context=<value optimized out>) at gmain.c:1814 #35 IA__g_main_context_dispatch (context=<value optimized out>) at gmain.c:2367 #36 0x00b777f8 in g_main_context_iterate (context=0x8c5d9c8, block=<value optimized out>, dispatch=1, self=0x8c30860) at gmain.c:2448 #37 0x00b77caf in IA__g_main_loop_run (loop=0x8cb0fe0) at gmain.c:2656 #38 0x02c96913 in bonobo_main () at bonobo-main.c:311 #39 0x0805d6bf in main ()
It seems it's quite busy in opening a folder and reading your summary. Did it ever recover after some time? I noticed the summary access can be sometimes quite slow.
Please use --disable-evolution-push-module during Tracker's configure. This plugin isn't functional in Tracker 0.6's releases. It will be made functional in Tracker's tracker-store branch (to be released as 0.7 alphas first) The problem will be the same, apparently there's a mail_get_folder() which is asynchronous. The plugin apparently calls a camel_store_get_folder() at a hook that evolution emitted from its mainloop (which apparently isn't allowed by Evolution).
Note that in later releases this plugin is by default disabled (not sure if we ever by default enabled it in Tracker 0.6, I don't think we did but not sure).
The plugin is disabled in the tracker-0.6.95 build (currently in testing). Bastien, can you please confirm tracker-0.6.95-1.fc11 in the update-testing repo doesn't cause problem?
tracker-0.6.96-1.fc12 has been submitted as an update for Fedora 12. http://admin.fedoraproject.org/updates/tracker-0.6.96-1.fc12
tracker-0.6.96-1.fc11 has been submitted as an update for Fedora 11. http://admin.fedoraproject.org/updates/tracker-0.6.96-1.fc11
tracker-0.6.96-1.fc11 has been pushed to the Fedora 11 testing repository. If problems still persist, please make note of it in this bug report. If you want to test the update, you can install it with su -c 'yum --enablerepo=updates-testing update tracker'. You can provide feedback for this update here: http://admin.fedoraproject.org/updates/F11/FEDORA-2010-1522
tracker-0.6.96-1.fc12 has been pushed to the Fedora 12 testing repository. If problems still persist, please make note of it in this bug report. If you want to test the update, you can install it with su -c 'yum --enablerepo=updates-testing update tracker'. You can provide feedback for this update here: http://admin.fedoraproject.org/updates/F12/FEDORA-2010-1525
tracker-0.6.96-2.fc12 has been submitted as an update for Fedora 12. http://admin.fedoraproject.org/updates/tracker-0.6.96-2.fc12
tracker-0.6.96-2.fc12 has been pushed to the Fedora 12 testing repository. If problems still persist, please make note of it in this bug report. If you want to test the update, you can install it with su -c 'yum --enablerepo=updates-testing update tracker'. You can provide feedback for this update here: http://admin.fedoraproject.org/updates/F12/FEDORA-2010-1615
This message is a reminder that Fedora 11 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 11. 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 '11'. 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 11'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 11 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 please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. 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. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Fedora 11 changed to end-of-life (EOL) status on 2010-06-25. Fedora 11 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.