Version-Release number of selected component: evolution-3.6.3-2.fc18 Additional info: backtrace_rating: 4 cmdline: evolution crash_function: g_hash_table_resize executable: /usr/bin/evolution kernel: 3.8.1-201.fc18.x86_64 uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #3 g_hash_table_resize at ghash.c:601 #4 g_hash_table_maybe_resize at ghash.c:630 #5 g_hash_table_insert_node at ghash.c:907 #6 g_hash_table_insert_internal at ghash.c:1153 #7 g_dbus_connection_signal_subscribe at gdbusconnection.c:3504 #8 async_initable_init_first at gdbusproxy.c:1780 #9 initable_init at gdbusproxy.c:1980 #10 g_initable_new_valist at ginitable.c:228 #11 g_initable_new at ginitable.c:148 #12 e_dbus_authenticator_proxy_new_for_bus_sync at e-dbus-authenticator.c:1286 Potential duplicate: bug 907519
Created attachment 705425 [details] File: backtrace
Created attachment 705426 [details] File: build_ids
Created attachment 705427 [details] File: cgroup
Created attachment 705428 [details] File: core_backtrace
Created attachment 705429 [details] File: dso_list
Created attachment 705430 [details] File: environ
Created attachment 705431 [details] File: limits
Created attachment 705432 [details] File: maps
Created attachment 705433 [details] File: open_fds
Created attachment 705434 [details] File: proc_pid_status
Created attachment 705435 [details] File: var_log_messages
The crash happened sometime yesterday or last night while I was away. I left evolution up and running to sync with exchange. Unsure as to the cause.
Thanks for a bug report. I see from the backtrace that this happened during the evolution-mapi account was trying to connect to your server, your machine might got disconnected unexpectedly, probably, and this was in a time to ask for a password. It crashed deep in the GDBus code, which is out of evolution, but it's possible it was caused by a memory corruption caused by evolution or any of its parts, including evolution-mapi. Unfortunately, if it's just a one-time crash, or basically unreproducible, then I'm afraid there's not much to be done to help to solve this issue, when it cannot be properly identified. I usually use valgrind to check for memory issues, but it's not guaranteed it'll help, and it's awfully slow with it. But I have an idea, could you run evolution from a terminal with this command, please? $ G_SLICE=debug-blocks evolution Then just use it. It may eventually "crash" evolution, when it finds an error. It's not that accurate, neither that powerful like valgrind, but it doesn't influence speed that much.
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.