Bug 808476 - Firefox crashing
Summary: Firefox crashing
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: firefox
Version: 15
Hardware: i686
OS: Linux
unspecified
urgent
Target Milestone: ---
Assignee: Martin Stransky
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-03-30 13:50 UTC by Tom Kovar
Modified: 2012-04-02 14:16 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-04-02 14:16:30 UTC
Type: ---

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description Tom Kovar 2012-03-30 13:50:34 UTC 
Description of problem:
Packagekit informed me there be a new to be installed update of FireFox (11.0-1). I did the installation, everything ran smoothly, but after the installation, FireFox cannot be started (immediately the Mozilla Crash Reporter comes up, independently of the parameters of the firefox call).


Version-Release number of selected component (if applicable):
firefox 11.0-1.fc15
fedora linux 2.6.38.6-26.rc1.fc15.i686

How reproducible:
as stated - every start ends up in the crash


Steps to Reproduce:
1. start firefox
2. get mad
3.
Comment 1 Tom Kovar 2012-03-30 13:55:26 UTC 
by "independently of the parameters" I mean that starting with -safe-mode or any other parameter does not change anything on the behaviour.
Comment 2 Martin Stransky 2012-03-30 14:15:51 UTC 
Can you attach a bactrace of the crash? (see http://fedoraproject.org/wiki/Debugging_guidelines_for_Mozilla_products).
Comment 3 Tom Kovar 2012-03-30 14:32:48 UTC 
Thanks, and sorry for bothering.
I have been playing in the meantime, and found out that *manually uninstalling* xulrunner and then reinstalling firefox solved the problem.
Do not ask me why, because after uninstalling xulrunner yum install firefox-11.0 installed xulrunner 11.0-3, which was the same version as installed before.
But now it seems to work...

Thanks again,
    --- Tom
Note You need to log in before you can comment on or make changes to this bug.