Bug 742357 - [abrt] evolution-2.32.3-1.fc14: talloc_chunk_from_ptr: Process /usr/bin/evolution was killed by signal 11 (SIGSEGV)
Summary: [abrt] evolution-2.32.3-1.fc14: talloc_chunk_from_ptr: Process /usr/bin/evolu...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: evolution-mapi
Version: 14
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Matthew Barnes
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:8a614e53386d47168511bd31159...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-09-29 20:15 UTC by Justin Bassignani
Modified: 2012-08-16 14:19 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-08-16 14:19:03 UTC
Type: ---


Attachments (Terms of Use)
File: backtrace (61.41 KB, text/plain)
2011-09-29 20:15 UTC, Justin Bassignani
no flags Details

Description Justin Bassignani 2011-09-29 20:15:43 UTC
abrt version: 1.1.18
architecture: x86_64
Attached file: backtrace, 62879 bytes
cmdline: evolution
comment: Evolution is using MAPI to connect to Exchange server, not sure if libmapi could be the culprit.
component: evolution
Attached file: coredump, 231845888 bytes
crash_function: talloc_chunk_from_ptr
executable: /usr/bin/evolution
kernel: 2.6.35.13-92.fc14.x86_64
package: evolution-2.32.3-1.fc14
rating: 4
reason: Process /usr/bin/evolution was killed by signal 11 (SIGSEGV)
release: Fedora release 14 (Laughlin)
time: 1317327184
uid: 500

How to reproduce
-----
1. Attempted to search by message body
2. Boom

Comment 1 Justin Bassignani 2011-09-29 20:15:45 UTC
Created attachment 525635 [details]
File: backtrace

Comment 2 Milan Crha 2011-09-30 09:19:11 UTC
Thanks for a bug report. I'm moving this to evolution-mapi. The crash happened on message opening, and I'm wondering whether this was fixed in the current version of OpenChange in F-16, which is openchange-0.11, together with some fixes in talloc itself, where I do not know, but maybe they addressed something from this as well. Are you able to give it a try in a virtual machine or something like that, please? It will be very helpful, together with a fact that F-14 is reaching its end of life quite quickly now.

Comment 3 Fedora End Of Life 2012-08-16 14:19:05 UTC
This message is a notice that Fedora 14 is now at end of life. Fedora 
has stopped maintaining and issuing updates for Fedora 14. It is 
Fedora's policy to close all bug reports from releases that are no 
longer maintained.  At this time, all open bugs with a Fedora 'version'
of '14' have been closed as WONTFIX.

(Please note: Our normal process is to give advanced warning of this 
occurring, but we forgot to do that. A thousand apologies.)

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, feel free to reopen 
this bug and simply change the 'version' to a later Fedora version.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we were unable to fix it before Fedora 14 reached 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 to click on 
"Clone This Bug" (top right of this page) and open it against that 
version of Fedora.

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


Note You need to log in before you can comment on or make changes to this bug.