Closed Bug 480959 Opened 15 years ago Closed 15 years ago

Search bar doesn´t work

Categories

(Firefox :: Search, defect)

Product:
Firefox
Component:
Search
Version:
3.5 Branch
Platform:
x86
Windows XP
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

()

Status:
RESOLVED DUPLICATE of bug 472064

People

(Reporter: victor_pachon, Unassigned)

Details

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; es-ES; rv:1.9.1b2) Gecko/20081201 Firefox/3.1b2
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; es-ES; rv:1.9.1b2) Gecko/20081201 Firefox/3.1b2

The integrated search bar doesn´t work anyway.

Reproducible: Always
What doesn't work? Please give more details. Clicking the dropdown? Entering a search term? Submitting the search?
Version: unspecified → 3.1 Branch
It doesn´t work submitting the search. I can enter the term or select a different motor but never makes the search.
Is it a new profile or have you used it to switch between Firefox 3.1 beta x and Firefox 3.0.x and vice versa?
I don´t know if i understood. I installed Firefox 3.1b2 but i still have installed 3.0.x (latest one). All my configuration stay without changes except for those add-ons wich weren´t compatible. In F3.0.x i was able to submitting searches in all searching engines.
Can you please do me a favor and test the following?

Go to your profile folder (http://support.mozilla.com/en-US/kb/Managing+profiles) and move away the signons.sqlite while Firefox is closed. Does the search bar work again after you have moved away this file? If yes, copy it back into the profile and use one of the latest nightly builds which will become beta 3. You can find it here: http://ftp.mozilla.org/pub/mozilla.org/firefox/nightly/latest-mozilla-1.9.1/
(In reply to comment #5)
> Can you please do me a favor and test the following?
> Go to your profile folder
> (http://support.mozilla.com/en-US/kb/Managing+profiles) and move away the
> signons.sqlite while Firefox is closed. Does the search bar work again after
> you have moved away this file? If yes, copy it back into the profile and use
> one of the latest nightly builds which will become beta 3. You can find it
> here:
> http://ftp.mozilla.org/pub/mozilla.org/firefox/nightly/latest-mozilla-1.9.1/

It didn´t work. I removed this file, run firefox again and search bar doesn´t work. I saw the file signons.sqlite is created again when I run firefox.
Please try the Firefox safemode first :
http://support.mozilla.com/en-US/kb/Safe+Mode
and if that doesn't help try to create a new profile:
http://support.mozilla.com/en-US/kb/Managing+profiles
(In reply to comment #7)
> Please try the Firefox safemode first :
> http://support.mozilla.com/en-US/kb/Safe+Mode
> and if that doesn't help try to create a new profile:
> http://support.mozilla.com/en-US/kb/Managing+profiles

Ok, in safe mode it doesn't work but I create a new profile and it works. It seems something is wrong with my old profile. But, why can I use the search bar in "old" firefox 3.0.x with this profile but not in 3.1b2?
(In reply to comment #6)
> It didn´t work. I removed this file, run firefox again and search bar doesn´t
> work. I saw the file signons.sqlite is created again when I run firefox.

Ok, so it is not related to the Satchel fix. Could you please try to run the latest 3.1b3? It would be good to know if this bug is still existent there.
(In reply to comment #9)
> (In reply to comment #6)
> > It didn´t work. I removed this file, run firefox again and search bar doesn´t
> > work. I saw the file signons.sqlite is created again when I run firefox.
> Ok, so it is not related to the Satchel fix. Could you please try to run the
> latest 3.1b3? It would be good to know if this bug is still existent there.

I will try 3.1b3, but can't be today. Tell me if there is any solution for this bug in 3.1b2. Thanks!!
I bet that his search engine configuration is broken. There is an addon that did something like that.

Reporter:
Can you please open about:config, confirm the warning and enter "search" in the filter bar at the top of the page.
is the value of browser.search.defaultenginename set to Google ?
If you left click on the search Engine (left side of the search bar) a menu should open with Manage search Engines. Is there an unusual Engine listed ?
Further you could make a backup of your profile and delete the prefs.js while Firefox is not running. Any user preferences will be reset-ed. If that helps a strange pref was set at some point. If not, go on and delete files step by step and restart Firefox in between to check if it is working. That way we can find the faulty pref or file. Thanks!
(In reply to comment #12)
> Further you could make a backup of your profile and delete the prefs.js while
> Firefox is not running. Any user preferences will be reset-ed. If that helps a
> strange pref was set at some point. If not, go on and delete files step by step
> and restart Firefox in between to check if it is working. That way we can find
> the faulty pref or file. Thanks!

I tried different things but with no solution of my problem: I deleted the prefs.js (and nothing), i deleted all my add-ons one by one (and nothing), I deleted some files from profiles (and nothing), changed some strings from about:config (and nothing at all). It seems to be a problem with my profile and new 3.1b (because i didn't that issue in 3.0.x nor with a new profile created for 3.1b). I will keep trying and if i get a solution i'll post. THank for your help and if you have new ideas, they will be welcome.
Victor, you should try to delete every file which is located inside the profile. Some of them will be recreated when Firefox is started. Please make sure that you delete them *only* when Firefox is closed. There has to be at least one faulty file because you say a new profile works for you.
(In reply to comment #14)
> Victor, you should try to delete every file which is located inside the
> profile. Some of them will be recreated when Firefox is started. Please make
> sure that you delete them *only* when Firefox is closed. There has to be at
> least one faulty file because you say a new profile works for you.

Hi! I solved my problem. I deleted every file from profile (previously backup) and run firefox, so as said, some were recreated. Then I copied (and overwrite) those which need of configuration, passwords, addons, etc (i can make a list if it's needed). Search bar works again. 
So, it seems a problem with my own profile but maybe there is something wrong "updating" it from F3.0.x to F3.1b that "broke" it (remember it worked in F3.0). It has to be considerated if more people have similar problems.
Thanks again for your help!
Status: UNCONFIRMED → RESOLVED
Closed: 15 years ago
Resolution: --- → FIXED
Please leave it open until we know which is the real cause of this problem. Have you identified which of the files are responsible for that behavior? We need this info to check what happens at all.
Status: RESOLVED → UNCONFIRMED
Resolution: FIXED → ---
I've had this problem frequently, on different computers and on different platforms. Search Box stops working (although I still get suggestions). When I press enter, nothing happens. 
Clicking on the "search" icons gives the following output to the error console:

Error: uncaught exception: [Exception... "Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsIFormHistory2.addEntry]"  nsresult: "0x80004005 (NS_ERROR_FAILURE)"  location: "JS frame :: chrome://browser/content/search/search.xml :: handleSearchCommand :: line 443"  data: no]

It's the same in safe mode. Deleting my profile helps.

This problem occurs almost always when the disk is full or my quota is reached, and sometimes after a crash / unclean exit.
Jason, you probably see the same issue as we have with our automated tests on Fennec. This is filed as bug 478212. Probably you should ask there.

Victor, it would be great if you could tell me if you have copied the formhistory.sqlite back too. Or if this file caused the problem.
If my above assumption is correct, it would be a dupe of bug 472064.
Thanks for the quick response.

Deleting formhistory.sqlite made it work again now. (I don't know if that's the only problematic file, as I deleted places.sqlite search.sqlite and urlclassifier* separately before. If I have another crash - what I don't hope - I'll try to narrow it down.)
Jason, if you still have the affected formhistory.sqlite run the sqlite commands given in bug 472064 comment 1. That should fix the database without loosing all the saved data.
Ok, everything on this bug looks like a broken formhistory.sqlite. The underlying cause was fixed in bug 472064. So duping it against. Steps how to solve this issue are given there.
Status: UNCONFIRMED → RESOLVED
Closed: 15 years ago → 15 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.