Closed Bug 338763 Opened 18 years ago Closed 15 years ago

Search toolbar doesn't respond to anything

Categories

(Firefox :: Search, defect)

Product:
Firefox
Component:
Search
Platform:
x86
Windows XP
Type:
defect
Priority:
Not set
Severity:
major

Tracking

()

Status:
RESOLVED INCOMPLETE

People

(Reporter: bjorn.nostvold, Unassigned)

References

Details

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1a2) Gecko/20060521 BonEcho/2.0a2
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1a2) Gecko/20060521 BonEcho/2.0a2

No search engines works in the Search toolbar.
Pressing enter or clicking on the magnifying glass does nothing.
Works in 1.5.0.x and latest Trunk.
Clean profile, etc. changes nothing.

Reproducible: Always

Steps to Reproduce:
1. Type something in the Search toolbar
2. Press enter or click on the magnifying glass
3. Nothing happens

Actual Results:  
Nothing happens

Expected Results:  
Results from selected search engine

I have seen other bugs where the Search toolbar is blank or impossible to add search engines. This bug is almost certainly not related to those bugs, it is possible to add and remove search engines, you just can't search with them.
If you set javascript.options.showInConsole to true using about:config, do you see any errors in the Javascript Console? How about if you set browser.search.log to true?
If you could paste any logs here, that'd be great.
I'm getting this in the Javascript Console:

getSubmission: In data: "test"

getSubmission: Out data: "test"

Error: uncaught exception: [Exception... "Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsISearchEngine.getSubmission]"  nsresult: "0x80004005 (NS_ERROR_FAILURE)"  location: "JS frame :: chrome://browser/content/search/search.xml :: doSearch :: line 379"  data: no]

The search toolbar works on my Mac (OS X 10.4.6)
Was this from a build you built yourself? See bug 338364, this sounds like a duplicate.
It could be the same or at least related issue, but I get all my builds from the mozilla ftp.
I noticed this bug a few weeks ago, but I changed back to the 1.5.0.x releases while waiting for a few other bugs to be resolved.
Can you send me the contents of your search plugin folders in a zip file? Usually those are "C:\program files\Mozilla Firefox\searchplugins" and "<your profile>\searchplugins", for windows.
Hmm, I'm unable to reproduce with the set that you sent me, and I'm really puzzled as to what in the code would trigger that error. It may be related to the fact that you have both the old-style and new-style plugins in your Firefox program dir (presumably the result of installing a new build over an old one).

In most cases the old style plugin is preferred (merely because ".src" comes before ".xml" in an alphabetical listing), but that shouldn't in itself cause any problems. I'll ask the reporter of bug 338364 if he was in the same situation.
I have similar problems with the search bar, however, I can usually get it to work again by restarting FF.  I'm running 2.0.0.3, and get the following error in the JS Console...

Error: [Exception... "Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [mozIStorageStatementWrapper.step]"  nsresult: "0x80004005 (NS_ERROR_FAILURE)"  location: "JS frame :: file:///C:/PROGRA~1/Mozilla%20Firefox/components/nsSearchService.js :: epsGetAttr :: line 2845"  data: no]
Source File: file:///C:/PROGRA~1/Mozilla%20Firefox/components/nsSearchService.js
Line: 2845

I am having this issue as well since I upgraded yesterday to Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.1b2) Gecko/20081201 Firefox/3.1b2. 

IT is possible that I placed the build over a previous build.

I always download Firefox from the Mozilla site...

I tried to follow the directions noted above and had the following error:

Error: uncaught exception: [Exception... "Component returned failure code: 0x80570016 (NS_ERROR_XPC_GS_RETURNED_FAILURE) [nsIJSCID.getService]"  nsresult: "0x80570016 (NS_ERROR_XPC_GS_RETURNED_FAILURE)"  location: "JS frame :: chrome://browser/content/search/search.xml :: initialize :: line 527"  data: no]
Mike, can you run a test with a fresh profile? See http://support.mozilla.com/en-US/kb/Managing+profiles
(In reply to comment #11)
> Mike, can you run a test with a fresh profile? See
> http://support.mozilla.com/en-US/kb/Managing+profiles

Henrik, as you requested, I ran the test with the fresh profile and the google search box operated as expected, pulling up the searched for data. So, the fresh profile resets whatever happened to stop the search bar function. 

I will do a search to see if it is possible to load some of my old settings into the new profile....

Thanks for your work on this!

Mike D.
A fresh profile may fix it for a while, but it may come back.  I created a fresh profile after I first experienced this problem, and it did not happen again for several months.  However, I just had it happen to me again in 3.0.6 about two weeks ago.  Simply restarting FF has always fixed it for me; at least temporarily.
Ok, everyone who sees this problem, please help us and do following test. Move the formhistory.sqlite out of the profile while Firefox is closed and try again. A new file will be created. Does it solve the unresponsiveness?
(In reply to comment #15)
> Ok, everyone who sees this problem, please help us and do following test. Move
> the formhistory.sqlite out of the profile while Firefox is closed and try
> again. A new file will be created. Does it solve the unresponsiveness?

So, after my earlier experiment today (creating new profile, opening new profile, then reopening old profile, after which the old and new profile both worked), it was working again. I did as you instructed above and deleted formhistory.sqlite out of my old profile. It continued to work just fine...

I hope this helps.

Mike D.
Matt and Bjorn, does comment 15 solves your problems too?
Ok, the lastest comments are showing another issue and should be solved by bug 472064. For a workaround how to restore the broken database you have to follow bug 472064 comment 1.

As the original reporter doesn't respond I'll set this bug as incomplete. Feel free to reopen if you can still see this problem.
Status: UNCONFIRMED → RESOLVED
Closed: 15 years ago
Resolution: --- → INCOMPLETE
(In reply to comment #17)
> Matt and Bjorn, does comment 15 solves your problems too?

It's hard to test.  In my case simply closing FF and restarting will restore the search toolbar functionality.  It sometimes goes months without having the problem.
Matt, when it will happen again, check the error console for any js error. It would even be helpful to enable strict js errors before in about:config. Just search for options.javascript.strict and set it to true. Please report back when it happens again. It should also be checked with the latest beta build of Firefox 3.5.
You need to log in before you can comment on or make changes to this bug.