Bug 553978

Summary: [abrt] crash in evolution-2.28.2-1 new_type_link
Product: [Fedora] Fedora Reporter: Dave <dave>
Component: evolutionAssignee: Matthew Barnes <mbarnes>
Status: CLOSED INSUFFICIENT_DATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: 12CC: lucilanga, mbarnes, mcepl, mcrha
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Linux   
Whiteboard: abrt_hash:650f55bfcd15d32a6754b58eba31df3fca27360a
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-05-11 17:53:04 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
File: backtrace none

Description Dave 2010-01-09 20:15:49 UTC 
abrt 1.0.3 detected a crash.

Attached file: backtrace
cmdline: evolution
component: evolution
executable: /usr/bin/evolution
kernel: 2.6.31.9-174.fc12.i686.PAE
package: evolution-2.28.2-1.fc12
rating: 3
reason: Process was terminated by signal 11 (Segmentation fault)
Comment 1 Dave 2010-01-09 20:15:52 UTC 
Created attachment 382705 [details]
File: backtrace
Comment 2 Milan Crha 2010-01-13 13:42:14 UTC 
Thanks for a bug report. The attached backtrace is missing some debug information, namely for gtk2. Could you install that and update the bug report, please?
Comment 3 Matěj Cepl 2010-02-26 12:14:52 UTC 
Could you please reply to the previous question? If you won't reply in one month, I will have to close this bug as INSUFFICIENT_DATA. Thank you.

[Note please, that this is machine generated comment for large amount of bugs; due to some technical issues, it is possible we've missed some of the responses -- it is happens, please, just a make a comment about that; that we will see. Thank you]
Comment 4 Matěj Cepl 2010-05-11 17:53:04 UTC 
Since there are insufficient details provided in this report for us to investigate the issue further, and we have not received feedback to the information we have requested above, we will assume the problem was not reproducible, or has been fixed in one of the updates we have released for the reporter's distribution.

Users who have experienced this problem are encouraged to upgrade to the latest update of their distribution, and if this issue turns out to still be reproducible in the latest update, please reopen this bug with additional information.

Closing as INSUFFICIENT_DATA.