Ubuntu
firefox-3.5 package

firefox search box gives out error message

Bug #609006 reported by marcosamson on 2010-07-23

This bug report is a duplicate of: Bug #338785: [MASTER] Updates while firefox is running cause various problems until restart. Edit Remove

This bug affects 1 person

Affects		Status	Importance	Assigned to	Milestone
	firefox-3.5 (Ubuntu)	Confirmed	Undecided	Unassigned

Bug Description

Binary package hint: firefox-3.5

ASSERT: *** Search: _installLocation: engine has no file!
Stack Trace:
0:ENSURE_WARN(false,_installLocation: engine has no file!,2147500037)
1:()
2:()
3:SRCH_ENG_getSubmission(tigerair+website,text/html)
4:getSubmission(tigerair+website,null)
5:doSearch(tigerair+website,current)
6:handleSearchCommand([object MouseEvent])
7:onclick([object MouseEvent])

ProblemType: Bug
Architecture: i386
Date: Fri Jul 23 13:01:05 2010
DistroRelease: Ubuntu 9.10
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5)
NonfreeKernelModules: nvidia
Package: firefox-3.5 3.6.7+build2+nobinonly-0ubuntu0.9.10.1
PackageArchitecture: all
ProcEnviron:
LANG=en_PH.UTF-8
SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-22.60-generic
SourcePackage: firefox-3.5
Uname: Linux 2.6.31-22-generic i686

Tags:

Revision history for this message

marcosamson (marcosamson) wrote on 2010-07-23:

Dependencies.txt Edit (3.4 KiB, text/plain; charset="utf-8")
ExtensionSummary.txt Edit (541 bytes, text/plain; charset="utf-8")
XsessionErrors.txt Edit (783 bytes, text/plain; charset="utf-8")
profile_default_pluginreg.dat.txt Edit (2.6 KiB, text/plain; charset="utf-8")
profiles.ini.txt Edit (94 bytes, text/plain; charset="utf-8")

Revision history for this message

Micah Gersten (micahg) wrote on 2010-07-23:

Please restart the browser after the upgrade.
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.