Bug 680224 - [abrt] thunderbird-3.0.10-1.fc12: Process /usr/lib64/thunderbird-3.0/thunderbird-bin was killed by signal 11 (SIGSEGV)
Summary: [abrt] thunderbird-3.0.10-1.fc12: Process /usr/lib64/thunderbird-3.0/thunderb...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: thunderbird
Version: 12
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Gecko Maintainer
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:43263a61cb0534f8935e035211b...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-02-24 18:04 UTC by rcorey
Modified: 2011-05-03 21:14 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-05-03 21:14:47 UTC
Type: ---


Attachments (Terms of Use)
File: backtrace (46.41 KB, text/plain)
2011-02-24 18:04 UTC, rcorey
no flags Details

Description rcorey 2011-02-24 18:04:04 UTC
abrt version: 1.1.13
architecture: x86_64
Attached file: backtrace
cmdline: /usr/lib64/thunderbird-3.0/thunderbird-bin
comment: Intermittant - doesn't seem to be reproducable
component: thunderbird
crash_function: nsProfileLock::FatalSignalHandler
executable: /usr/lib64/thunderbird-3.0/thunderbird-bin
kernel: 2.6.32.26-175.fc12.x86_64
package: thunderbird-3.0.10-1.fc12
rating: 4
reason: Process /usr/lib64/thunderbird-3.0/thunderbird-bin was killed by signal 11 (SIGSEGV)
release: Fedora release 12 (Constantine)
time: 1298567267
uid: 500

How to reproduce
-----
1. Occured on initial start of Thunderbird after a cold boot
2. Subsequent start of Thunderbird works fine
3. This is the 4th instance of this crash

Comment 1 rcorey 2011-02-24 18:04:06 UTC
Created attachment 480823 [details]
File: backtrace

Comment 2 Arif Tri Waluyo 2011-05-03 21:14:47 UTC
Thank you for your bug report.

We are sorry, but the Fedora Project is no longer releasing bug fixes or any other updates for this version of Fedora. This bug will be set to CLOSED:WONTFIX to reflect this, but please reopen it if the problem persists after upgrading to the latest version of Fedora, which is available from:

http://fedoraproject.org/get-fedora



-- 
Fedora Bugzappers volunteer triage team
https://fedoraproject.org/wiki/BugZappers


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