Bug 595312

Summary: [abrt] crash in claws-mail-3.7.5-2.fc12: Process /usr/bin/claws-mail was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: David Kovalsky <dkovalsk>
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: 12CC: andreas.bierfert, benl
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard: abrt_hash:a9326763f15178f653ad39867c72dec3f1b57a42
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-05-25 10:33:01 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 David Kovalsky 2010-05-24 10:56:01 UTC
abrt 1.0.9 detected a crash.

architecture: x86_64
Attached file: backtrace
cmdline: claws-mail
comment: Replied to an email, removed a couple of recipients from CC (icon on the right), and used mouse middle button (scroll) do change the email account. Boom!
component: claws-mail
crash_function: compose_show_first_last_header
executable: /usr/bin/claws-mail
global_uuid: a9326763f15178f653ad39867c72dec3f1b57a42
kernel: 2.6.32.12-115.fc12.x86_64
package: claws-mail-3.7.5-2.fc12
rating: 4
reason: Process /usr/bin/claws-mail was killed by signal 11 (SIGSEGV)
release: Fedora release 12 (Constantine)

How to reproduce
-----
1. Random crash, first one I've seen

Comment 1 David Kovalsky 2010-05-24 10:56:04 UTC
Created attachment 416085 [details]
File: backtrace

Comment 2 Karel Klíč 2010-05-25 10:33:01 UTC

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

Comment 3 Karel Klíč 2010-05-25 10:33:01 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 #543899.

Sorry for the inconvenience.