Red Hat Bugzilla – Bug 1029393
[abrt] evolution-3.8.5-2.fc19: talloc_chunk_from_ptr: Process /usr/bin/evolution was killed by signal 11 (SIGSEGV)
Last modified: 2015-02-17 14:12:08 EST
Version-Release number of selected component:
runlevel: N 5
Thread no. 1 (10 frames)
#0 talloc_chunk_from_ptr at ../talloc.c:370
#1 _talloc_free at ../talloc.c:1448
#2 smb_iconv_close at ../lib/util/charset/iconv.c:317
#3 close_iconv_handle at ../lib/util/charset/codepoints.c:211
#4 smb_iconv_handle_reinit at ../lib/util/charset/codepoints.c:239
#5 smb_iconv_handle_reinit_lp at ../lib/param/util.c:251
#6 reload_charcnv at ../lib/param/loadparm.c:2558
#7 lpcfg_update at ../lib/param/loadparm.c:2309
#8 lpcfg_load at ../lib/param/loadparm.c:2384
#9 loadparm_init_global at ../lib/param/loadparm.c:2257
Created attachment 822816 [details]
Created attachment 822817 [details]
Created attachment 822818 [details]
Created attachment 822819 [details]
Created attachment 822820 [details]
Created attachment 822821 [details]
Created attachment 822822 [details]
Created attachment 822823 [details]
Created attachment 822824 [details]
Created attachment 822825 [details]
Created attachment 822826 [details]
Thanks for a bug report. I see from the backtrace that this crashed when evolution was trying to connect to a MAPI account. I do not see why exactly this happened, unfortunately. Did this happen for you multiple times, or it's just for the first time, and the next start works as expected? The talloc memory manager claims about incorrect pointer, which can mean that there happened some use-after-free or anything similar for some reason, which are usually hard to reproduce, though without a reproducer it's even harder to fix it properly.
This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component.
This message is a notice that Fedora 19 is now at end of life. Fedora
has stopped maintaining and issuing updates for Fedora 19. It is
Fedora's policy to close all bug reports from releases that are no
longer maintained. Approximately 4 (four) weeks from now this bug will
be closed as EOL if it remains open with a Fedora 'version' of '19'.
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.
Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 19 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 this bug is closed as described in the policy above.
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 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 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
Thank you for reporting this bug and we are sorry it could not be fixed.