Description of problem: Crash report shows at login. KDE desktop but running Evolution for the Exchange connection. Version-Release number of selected component: evolution-3.6.3-2.fc18 Additional info: backtrace_rating: 4 cmdline: evolution arethusa26 crash_function: talloc_abort executable: /usr/bin/evolution kernel: 3.7.4-204.fc18.x86_64 remote_result: NOTFOUND uid: 1001 var_log_messages: Feb 4 12:53:05 pna-desk abrt[8938]: Saved core dump of pid 8914 (/usr/bin/evolution) to /var/spool/abrt/ccpp-2013-02-04-12:53:04-8914 (126832640 bytes) Truncated backtrace: Thread no. 1 (10 frames) #2 talloc_abort at ../talloc.c:317 #3 talloc_abort_access_after_free at ../talloc.c:336 #4 talloc_chunk_from_ptr at ../talloc.c:357 #6 __talloc at ../talloc.c:555 #7 talloc_named at ../talloc.c:1133 #8 smb_iconv_open_ex at ../lib/util/charset/iconv.c:205 #9 get_conv_handle at ../lib/util/charset/codepoints.c:285 #11 convert_string_talloc_handle at ../lib/util/charset/convert_string.c:388 #12 convert_string_talloc at ../lib/util/charset/convert_string.c:541 #13 ndr_pull_charset at ../librpc/ndr/ndr_string.c:593 Potential duplicate: bug 871799
Created attachment 693268 [details] File: backtrace
Created attachment 693270 [details] File: cgroup
Created attachment 693272 [details] File: core_backtrace
Created attachment 693274 [details] File: dso_list
Created attachment 693276 [details] File: environ
Created attachment 693278 [details] File: limits
Created attachment 693280 [details] File: maps
Created attachment 693281 [details] File: open_fds
Created attachment 693282 [details] File: proc_pid_status
Thanks for a bug report. I'm not sure, but maybe this is related to bug #903045. Could you try with evolution-mapi-3.6.3-2, please? Check bug #903045 for instructions how to get it from updates-testing.
I tried to install evolution-mapi 3.6.3-2 from updates-testing but then evolution just silently fails to start (no error message in a terminal).
Can there be any evolution running in the background? You can check that with: $ ps ax | grep evolution
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.