Bug 635307 - [abrt] thunderbird-3.1.3-1.fc13: Process /usr/lib/thunderbird-3.1/thunderbird-bin was killed by signal 11 (SIGSEGV)
Summary: [abrt] thunderbird-3.1.3-1.fc13: Process /usr/lib/thunderbird-3.1/thunderbird...
Keywords:
Status: CLOSED DUPLICATE of bug 626751
Alias: None
Product: Fedora
Classification: Fedora
Component: thunderbird
Version: 13
Hardware: i686
OS: Linux
low
medium
Target Milestone: ---
Assignee: Gecko Maintainer
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:aa771973114905560be6157a2dc...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-09-18 21:48 UTC by Nigel Horne
Modified: 2010-11-08 18:02 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-11-08 18:02:33 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: backtrace (92.29 KB, text/plain)
2010-09-18 21:48 UTC, Nigel Horne
no flags Details

Description Nigel Horne 2010-09-18 21:48:04 UTC
abrt version: 1.1.13
architecture: i686
Attached file: backtrace
cmdline: /usr/lib/thunderbird-3.1/thunderbird-bin
comment: Why is this software so buggy?  Don't you bother to test your software?
component: thunderbird
crash_function: nsProfileLock::FatalSignalHandler
executable: /usr/lib/thunderbird-3.1/thunderbird-bin
kernel: 2.6.34.6-54.fc13.i686
package: thunderbird-3.1.3-1.fc13
rating: 4
reason: Process /usr/lib/thunderbird-3.1/thunderbird-bin was killed by signal 11 (SIGSEGV)
release: Fedora release 13 (Goddard)
time: 1284846283
uid: 500

How to reproduce
-----
1. I clicked on an email in my Inbox and Thunderbird died (again!)
2.
3.

Comment 1 Nigel Horne 2010-09-18 21:48:11 UTC
Created attachment 448234 [details]
File: backtrace

Comment 2 Karel Klíč 2010-11-08 18:02:33 UTC

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

Comment 3 Karel Klíč 2010-11-08 18:02:33 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 #626751.

Sorry for the inconvenience.


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