Bug 633621

Summary: [abrt] firefox-3.5.11-1.fc12: Process /usr/lib/firefox-3.5/firefox was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: Jesse Larrew <jlarrew>
Component: firefoxAssignee: Gecko Maintainer <gecko-bugs-nobody>
Status: CLOSED WONTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: 12CC: gecko-bugs-nobody, jeff.raber
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Linux   
Whiteboard: abrt_hash:b933ea9ab10fc6b10c4e4ab1cf72baab91655169
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-12-03 12:30:49 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
File: backtrace none

Description Jesse Larrew 2010-09-14 03:19:49 UTC
abrt version: 1.1.13
architecture: i686
Attached file: backtrace
cmdline: /usr/lib/firefox-3.5/firefox
comment: I updated krb5 today, which explains the library location mismatch. 
component: firefox
executable: /usr/lib/firefox-3.5/firefox
kernel: 2.6.32.21-166.fc12.i686.PAE
package: firefox-3.5.11-1.fc12
rating: 3
reason: Process /usr/lib/firefox-3.5/firefox was killed by signal 11 (SIGSEGV)
release: Fedora release 12 (Constantine)
time: 1284434111
uid: 500

How to reproduce
-----
1. Close firefox.
2. Boom.
3.

Comment 1 Jesse Larrew 2010-09-14 03:19:51 UTC
Created an attachment (id=447113)
File: backtrace

Comment 2 Jeff Raber 2010-09-14 04:29:32 UTC
This does not look to be the same crash as reported in bug 543165.  

Does removing flash improve the situation?  
What is /usr/lib/mozilla/plugins/npgpws.so?

Comment 3 Jesse Larrew 2010-09-24 22:32:54 UTC
Thanks for looking into it Jeff!

/usr/lib/mozilla/plugins/npgpws.so is an IBM-specific firefox plugin that we use to locate and configure network printers when we travel to other sites. I've tried disabling this plugin, and firefox still crashes intermittently. I disabled flash, and I can't reproduce the crash. I updated to firefox-3.5.12-1.fc12.i686 and the results are the same: no flash = no crash while closing.

Jesse

Comment 4 Bug Zapper 2010-11-03 10:11:16 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: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 5 Bug Zapper 2010-12-03 12:30:49 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.