Error Message after Upgrade upon restart or New Windows

[redkirk]

Binary package hint: firefox-3.0

Ubuntu 8.04.3 LTS
synaptic 0.61ubuntu9

Commit Log for Fri Dec 18 19:40:32 2009
Upgraded the following packages:
firefox (3.0.15+nobinonly-0ubuntu0.8.04.1) to 3.0.16+nobinonly-0ubuntu0.8.04.1
firefox-3.0 (3.0.15+nobinonly-0ubuntu0.8.04.1) to 3.0.16+nobinonly-0ubuntu0.8.04.1
firefox-3.0-gnome-support (3.0.15+nobinonly-0ubuntu0.8.04.1) to 3.0.16+nobinonly-0ubuntu0.8.04.1
firefox-gnome-support (3.0.15+nobinonly-0ubuntu0.8.04.1) to 3.0.16+nobinonly-0ubuntu0.8.04.1
xulrunner-1.9 (1.9.0.15+nobinonly-0ubuntu0.8.04.1) to 1.9.0.16+nobinonly-0ubuntu0.8.04.1
xulrunner-1.9-gnome-support (1.9.0.15+nobinonly-0ubuntu0.8.04.1) to 1.9.0.16+nobinonly-0ubuntu0.8.04.1

I expected to restart FireFox and browse without error messages.
Upon restart, new window:

ASSERT: *** Serch: _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],32)

When copying highlight text and right-click to copy:
ASSERT: *** Serch: _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:() 9:CM_initMENU([object XULElement], [object XULElement]) 10:nsContextMenu([object XULElement],[object XULElement]) 11:onpopuipshowing([[object MouseEvent])

ProblemType: Bug
Architecture: i386
Date: Fri Dec 18 19:50:50 2009
DistroRelease: Ubuntu 8.04
Package: firefox-3.0 3.0.16+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-26-rt i686

[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.