Bug 679749

Summary: [abrt] thunderbird-3.1.7-2.fc14: Process /usr/lib/thunderbird-3.1/thunderbird-bin was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: michael <michaelsefi>
Component: thunderbirdAssignee: Gecko Maintainer <gecko-bugs-nobody>
Status: CLOSED INSUFFICIENT_DATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 14CC: gecko-bugs-nobody
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Unspecified   
Whiteboard: abrt_hash:cc40aca875f90966378bfdaf2fa7ce7e912c0e93
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-12-07 13:03:35 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
File: backtrace none

Description michael 2011-02-23 12:31:20 UTC 
abrt version: 1.1.17
architecture: i686
Attached file: backtrace, 107536 bytes
cmdline: /usr/lib/thunderbird-3.1/thunderbird-bin
component: thunderbird
Attached file: coredump, 285601792 bytes
crash_function: nsProfileLock::FatalSignalHandler
executable: /usr/lib/thunderbird-3.1/thunderbird-bin
kernel: 2.6.35.11-83.fc14.i686
package: thunderbird-3.1.7-2.fc14
rating: 4
reason: Process /usr/lib/thunderbird-3.1/thunderbird-bin was killed by signal 11 (SIGSEGV)
release: Fedora release 14 (Laughlin)
time: 1298464012
uid: 500

How to reproduce
-----
1.openened
2.started checking
3.crashed
Comment 1 michael 2011-02-23 12:31:24 UTC 
Created attachment 480439 [details]
File: backtrace
Comment 2 michael 2011-02-23 12:51:28 UTC 
Package: thunderbird-3.1.7-2.fc14
Architecture: i686
OS Release: Fedora release 14 (Laughlin)


How to reproduce
-----
1.openened
2.started checking
3.crashed
Comment 3 Martin Stransky 2011-12-07 13:03:35 UTC 
We're using mozilla crash reporter now, ABRT is no more used for Firefox/Thunderbird. If you can reliably reproduce the crash (you have a testcase, reproduction steps, etc.) please reopen the bug and attach the reproduction info and assign it directly to me (stransky).

Thanks!