When opening a new browser

[Zelda]

Binary package hint: firefox-3.0

whenever opening FF, the opening page flashes this message.

ASSERT: *** Search: _installLocation: engine has no file!
Stack Trace:
0:ENSURE_WARN(false,_installLocation: engine has no file!,2147500037)
1:()
2:()
3:()
4:epsGetAttr([object Object],hidden)
5:()
6:()
7:currentEngine()
8:get_currentEngine()
9:updateDisplay()
10:init()
11:([object XULElement],84)

ProblemType: Bug
Architecture: i386
Date: Fri Nov 20 11:50:13 2009
DistroRelease: Ubuntu 8.04
Package: firefox-3.0 3.0.15+nobinonly-0ubuntu0.8.04.1
PackageArchitecture: i386
ProcEnviron:
 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: firefox-3.0
Uname: Linux 2.6.24-25-generic i686

[Dan Buhrman (dan-buhrman)]

This looks like FF is having an issue with xulrunner. Try reinstalling xulrunner-1.9. (sudo apt-get purge xulrunner-1.9 && sudo apt-get install xulrunner-1.9)

Have you added any new extensions or made any changes recently to Firefox?

[Micah Gersten (micahg)]

This commonly happens after an upgrade when Firefox isn't restarted. Did you upgrade recently?

[Zelda (zjay)]

Possible, I am dealing with another issue on this pc. So I have been
trying to keep this pc up to date as much as possible. The other issue
is a failure to print in evolution.

On Sat, 2009-11-21 at 23:30 +0000, Micah Gersten wrote:

> This commonly happens after an upgrade when Firefox isn't restarted.
> Did you upgrade recently?
>
> ** Changed in: firefox-3.0 (Ubuntu)
> Status: In Progress => Incomplete
>
> ** Changed in: firefox-3.0 (Ubuntu)
> Assignee: dvlchd3 (dan-buhrman) => (unassigned)
>

[Micah Gersten (micahg)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 338785, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.