Bug 584789 - [abrt] crash in thunderbird-3.0.4-1.fc12: Process /usr/lib/thunderbird-3.0/thunderbird-bin was killed by signal 11 (SIGSEGV)
[abrt] crash in thunderbird-3.0.4-1.fc12: Process /usr/lib/thunderbird-3.0/th...
Product: Fedora
Classification: Fedora
Component: abrt (Show other bugs)
i686 Linux
low Severity medium
: ---
: ---
Assigned To: Denys Vlasenko
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2010-04-22 08:21 EDT by William Henry
Modified: 2010-12-03 10:35 EST (History)
8 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2010-12-03 10:35:30 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
File: backtrace (41.79 KB, text/plain)
2010-04-22 08:21 EDT, William Henry
no flags Details

  None (edit)
Description William Henry 2010-04-22 08:21:32 EDT
abrt 1.0.8 detected a crash.

architecture: i686
Attached file: backtrace
cmdline: /usr/lib/thunderbird-3.0/thunderbird-bin
comment: Thunderbird and Firefox crashed simultaneously?
component: thunderbird
executable: /usr/lib/thunderbird-3.0/thunderbird-bin
package: thunderbird-3.0.4-1.fc12
rating: 3
reason: Process /usr/lib/thunderbird-3.0/thunderbird-bin was killed by signal 11 (SIGSEGV)
release: Fedora release 12 (Constantine)

How to reproduce
Comment 1 William Henry 2010-04-22 08:21:36 EDT
Created attachment 408308 [details]
File: backtrace
Comment 2 William Henry 2010-04-22 08:29:16 EDT
Firefox and Thunderbird crashed simultaneously link to crash info here https://bugzilla.redhat.com/show_bug.cgi?id=584782
Comment 3 Chris Campbell 2010-05-14 08:17:51 EDT
#3  <signal handler called>
No symbol table info available.
#4  _cairo_gstate_restore (gstate=0xaecc781c, freelist=0xaecc7984)
    at cairo-gstate.c:259
        top = 0xf473b900
#5  0x006014a5 in cairo_restore (cr=0xaecc7800) at cairo.c:362
        status = <value optimized out>
#6  0x03bc6944 in gfxContext::Restore() ()
   from /usr/lib/thunderbird-3.0/libthebes.so
No symbol table info available.
#7  0x05039e28 in ?? ()
   from /usr/lib/thunderbird-3.0/components/libgkgfxthebes.so
No symbol table info available.
#8  0x019f0533 in ?? ()
   from /usr/lib/thunderbird-3.0/components/libgklayout.so
No symbol table info available.
#9  0x019f0352 in ?? ()
   from /usr/lib/thunderbird-3.0/components/libgklayout.so
No symbol table info available.
#10 0x01a02613 in ?? ()
   from /usr/lib/thunderbird-3.0/components/libgklayout.so
No symbol table info available.
#11 0x01a0a506 in ?? ()
   from /usr/lib/thunderbird-3.0/components/libgklayout.so
No symbol table info available.
#12 0x01c954b0 in ?? ()
   from /usr/lib/thunderbird-3.0/components/libgklayout.so
No symbol table info available.
#13 0x01c95b3c in ?? ()
   from /usr/lib/thunderbird-3.0/components/libgklayout.so
No symbol table info available.
#14 0x01c96105 in ?? ()
   from /usr/lib/thunderbird-3.0/components/libgklayout.so
No symbol table info available.
#15 0x01c91840 in ?? ()
   from /usr/lib/thunderbird-3.0/components/libgklayout.so
No symbol table info available.
#16 0x066a1514 in ?? ()
   from /usr/lib/thunderbird-3.0/components/libwidget_gtk2.so
No symbol table info available.
#17 0x066aafad in ?? ()
   from /usr/lib/thunderbird-3.0/components/libwidget_gtk2.so
No symbol table info available.

Fedora Bugzappers volunteer triage team
Comment 4 Chris Campbell 2010-05-14 08:19:18 EDT
Thank you for taking the time to report this crash.

Unfortunately, the stack trace is not very useful in determining the cause of the crash, because it lacks debugging symbols. This is likely due to a bug in ABRT, which should have captured this information automatically. I am reassigning this bug to ABRT for diagnosis; if it can be fixed, you should be able to automatically generate a useful report for this crash in the future. 

In the meantime, if you are interested in attempting to diagnose the crash itself, you can try installing debuginfo packages manually, which will hopefully provide debugging symbols in the next stack trace. You can run the command: 

    debuginfo-install PROGRAMNAMEHERE 

Please see http://fedoraproject.org/wiki/StackTraces for more information about obtaining stack traces manually. If you successfully obtain a better stack trace, please report it under a separate bug and add a comment to this bug with the new bug number (since this bug will track the ABRT fix, not the crash fix)

Fedora Bugzappers volunteer triage team
Comment 5 Bug Zapper 2010-11-03 12:35:31 EDT
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 6 Bug Zapper 2010-12-03 10:35:30 EST
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.