Bug 632679 - [abrt] thunderbird-3.1.3-1.fc13: Process /usr/lib64/thunderbird-3.1/thunderbird-bin was killed by signal 11 (SIGSEGV)
Summary: [abrt] thunderbird-3.1.3-1.fc13: Process /usr/lib64/thunderbird-3.1/thunderbi...
Keywords:
Status: CLOSED DUPLICATE of bug 596865
Alias: None
Product: Fedora
Classification: Fedora
Component: thunderbird
Version: 13
Hardware: x86_64
OS: Linux
low
medium
Target Milestone: ---
Assignee: Gecko Maintainer
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:417ab9e8821c89c203948e6a02f...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-09-10 18:04 UTC by Emmett Culley
Modified: 2010-11-08 17:06 UTC (History)
1 user (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2010-11-08 17:06:55 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: backtrace (173.71 KB, text/plain)
2010-09-10 18:04 UTC, Emmett Culley
no flags Details

Description Emmett Culley 2010-09-10 18:04:08 UTC
abrt version: 1.1.13
architecture: x86_64
Attached file: backtrace
cmdline: /usr/lib64/thunderbird-3.1/thunderbird-bin
comment: Attempting a body search.  Crashed when I clicked on the "broom" to drop search.
component: thunderbird
crash_function: nsProfileLock::FatalSignalHandler
executable: /usr/lib64/thunderbird-3.1/thunderbird-bin
kernel: 2.6.34.6-54.fc13.x86_64
package: thunderbird-3.1.3-1.fc13
rating: 4
reason: Process /usr/lib64/thunderbird-3.1/thunderbird-bin was killed by signal 11 (SIGSEGV)
release: Fedora release 13 (Goddard)
time: 1284141136
uid: 500

How to reproduce
-----
1. Entered search term
2. Clicked "broom" to clear search
3. Crashed

Comment 1 Emmett Culley 2010-09-10 18:04:12 UTC
Created an attachment (id=446573)
File: backtrace

Comment 2 Karel Klíč 2010-11-08 17:06:55 UTC

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

Comment 3 Karel Klíč 2010-11-08 17:06:55 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 #596865.

Sorry for the inconvenience.


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