Bug 678358 - [abrt] thunderbird-3.1.7-2.fc14: Process /usr/lib/thunderbird-3.1/thunderbird-bin was killed by signal 11 (SIGSEGV)
Summary: [abrt] thunderbird-3.1.7-2.fc14: Process /usr/lib/thunderbird-3.1/thunderbird...
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Fedora
Classification: Fedora
Component: thunderbird
Version: 14
Hardware: i686
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Gecko Maintainer
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:3a0f7f4e32015d6630a22c5f9e1...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-02-17 17:10 UTC by Ken Dubrick
Modified: 2011-12-07 13:17 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-12-07 13:17:16 UTC
Type: ---


Attachments (Terms of Use)
File: backtrace (94.06 KB, text/plain)
2011-02-17 17:10 UTC, Ken Dubrick
no flags Details

Description Ken Dubrick 2011-02-17 17:10:11 UTC
abrt version: 1.1.14
architecture: i686
Attached file: backtrace
cmdline: /usr/lib/thunderbird-3.1/thunderbird-bin
component: thunderbird
executable: /usr/lib/thunderbird-3.1/thunderbird-bin
kernel: 2.6.35.11-83.fc14.i686
package: thunderbird-3.1.7-2.fc14
reason: Process /usr/lib/thunderbird-3.1/thunderbird-bin was killed by signal 11 (SIGSEGV)
release: Fedora release 14 (Laughlin)
time: 1297962262
uid: 500

comment
-----
I had just finished running some updates and was going to check my mail.
Opened it up and it crashed right away... First time Tbird has crashed on me

How to reproduce
-----
1. Just opened it up
2.
3.

Comment 1 Ken Dubrick 2011-02-17 17:10:13 UTC
Created attachment 479366 [details]
File: backtrace

Comment 2 Martin Stransky 2011-12-07 13:17:16 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!


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