Ubuntu
firefox-3.0 package

Error message when typing in adress field

Bug #429347 reported by Patwotrik on 2009-09-14

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.0 (Ubuntu)	New	Undecided	Unassigned

Bug Description

Binary package hint: firefox-3.0

When I type an adress and press enter I get an error 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],alias)
5:()
6:SRCH_SVC_getEngineByAlias(google.se)
7:getEngineByAlias(google.se)
8:getShortcutOrURI(google.se,[object Object])
9:canonizeUrl([object KeyboardEvent],[object Object])
10:handleURLBarCommand([object KeyboardEvent])
11:anonymous(textentered,[object KeyboardEvent])
12:fireEvent(textentered,[object KeyboardEvent])
13:onTextEntered()
14:handleEnter(false)
15:onKeyPress([object KeyboardEvent])
16:onxblkeypress([object KeyboardEvent])

ProblemType: Bug
Architecture: amd64
DistroRelease: Ubuntu 9.04
Package: firefox-3.0 3.0.14+build2+nobinonly-0ubuntu0.9.04.1
ProcEnviron:
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: firefox-3.0
Uname: Linux 2.6.28-14-generic x86_64

Tags:

Revision history for this message

Patwotrik (patrik-broman) wrote on 2009-09-14:

Dependencies.txt Edit (3.2 KiB, text/plain; charset="utf-8")
ExtensionSummary.txt Edit (550 bytes, 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 2009-09-15:

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.