Bug 637080

Summary: [abrt] claws-mail-3.7.6-1.fc14.1: _int_malloc: Process /usr/bin/claws-mail was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: Adrien Bustany <adrien-xx-redhatbz>
Component: claws-mailAssignee: Andreas Bierfert <andreas.bierfert>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: 14CC: andreas.bierfert, bugs.michael
Target Milestone: ---Keywords: Reopened
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard: abrt_hash:d3947bad29f228b797e9679da9152b28fbfc8e04
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-11-12 15:21:02 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 Adrien Bustany 2010-09-24 08:23:36 UTC 
abrt version: 1.1.13
architecture: x86_64
Attached file: backtrace
cmdline: claws-mail
component: claws-mail
crash_function: _int_malloc
executable: /usr/bin/claws-mail
kernel: 2.6.35.4-28.fc14.x86_64
package: claws-mail-3.7.6-1.fc14.1
rating: 4
reason: Process /usr/bin/claws-mail was killed by signal 11 (SIGSEGV)
release: Fedora release 14 (Laughlin)
time: 1285313403
uid: 500

How to reproduce
-----
1. Resume from suspend to RAM, network was down and is coming back, probably a stale IMAP connection is not valid anymore in claws
Comment 1 Adrien Bustany 2010-09-24 08:23:39 UTC 
Created attachment 449363 [details]
File: backtrace
Comment 2 Karel Klíč 2010-11-09 16:19:05 UTC 

*** This bug has been marked as a duplicate of bug 630828 ***
Comment 3 Karel Klíč 2010-11-09 16:19:05 UTC 
This bug appears to have been filled using a buggy version of ABRT, because
it contains a backtrace which is a duplicate of backtrace from bug #630828.

Sorry for the inconvenience.
Comment 4 Michael Schwendt 2010-11-12 15:21:02 UTC 

*** This bug has been marked as a duplicate of bug 617985 ***