Bug 588883 - [abrt] crash in thunderbird-3.0.4-1.fc12: Process /usr/lib64/thunderbird-3.0/thunderbird-bin was killed by signal 11 (SIGSEGV)
Summary: [abrt] crash in thunderbird-3.0.4-1.fc12: Process /usr/lib64/thunderbird-3.0/...
Alias: None
Product: Fedora
Classification: Fedora
Component: thunderbird
Version: 12
Hardware: x86_64
OS: Linux
Target Milestone: ---
Assignee: Gecko Maintainer
QA Contact: Fedora Extras Quality Assurance
Whiteboard: abrt_hash:3fba8b2c7b0b1fce3e43c33bfc4...
Depends On:
TreeView+ depends on / blocked
Reported: 2010-05-04 18:44 UTC by Scott Castaline
Modified: 2018-04-11 07:03 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2010-12-03 15:05:47 UTC
Type: ---

Attachments (Terms of Use)
File: backtrace (104.63 KB, text/plain)
2010-05-04 18:44 UTC, Scott Castaline
no flags Details
Part of the thread where crash happened (7.36 KB, text/plain)
2010-09-24 17:03 UTC, Matěj Cepl
no flags Details

Description Scott Castaline 2010-05-04 18:44:30 UTC
abrt 1.0.9 detected a crash.

architecture: x86_64
Attached file: backtrace
cmdline: /usr/lib64/thunderbird-3.0/thunderbird-bin
comment: I wasn't around when it happened. I had Firefox minimized with 2 tabs running, Thunderbird minimized with calendar tab as active, GnuCash minimized, an OpenOffice.org Spreadsheet minimized as well as calculator and Keepassx, both were minimized. Thunderbird is setup to receive IMAP mail from gmail and POP3 mail from comcast. Lightning is set for bidirectional use of my personal google calendar overlayed on my local calendar as well as receive only 2 optional or additional calendars from Google.
component: thunderbird
executable: /usr/lib64/thunderbird-3.0/thunderbird-bin
global_uuid: 3fba8b2c7b0b1fce3e43c33bfc46e71afd7d2ae2
package: thunderbird-3.0.4-1.fc12
rating: 4
reason: Process /usr/lib64/thunderbird-3.0/thunderbird-bin was killed by signal 11 (SIGSEGV)
release: Fedora release 12 (Constantine)

How to reproduce
1.Started Thunderbird and checked email.
2.Switched back to calendar tab and minimized

Comment 1 Scott Castaline 2010-05-04 18:44:33 UTC
Created attachment 411366 [details]
File: backtrace

Comment 2 Matěj Cepl 2010-09-24 17:03:38 UTC
Created attachment 449463 [details]
Part of the thread where crash happened

Comment 3 Bug Zapper 2010-11-03 15:39:30 UTC
This message is a reminder that Fedora 12 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 12.  It is Fedora's policy to close all
bug reports from releases that are no longer maintained.  At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '12'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 12's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 12 is end of life.  If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events.  Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 

Comment 4 Bug Zapper 2010-12-03 15:05:47 UTC
Fedora 12 changed to end-of-life (EOL) status on 2010-12-02. Fedora 12 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.

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