Closed Bug 585447 Opened 15 years ago Closed 7 years ago

Toolbar Search Field is not removable, reappears upon FF restart

Categories

(Firefox :: Search, defect)

x86_64
Windows 7
defect
Not set
normal

Tracking

()

RESOLVED INCOMPLETE

People

(Reporter: aimankhan, Unassigned)

Details

User-Agent: Mozilla/5.0 (Windows; Windows NT 6.1; WOW64; rv:2.0b2) Gecko/20100720 Firefox/4.0b2 (.NET CLR 3.5.30729) Build Identifier: Mozilla/5.0 (Windows; Windows NT 6.1; WOW64; rv:2.0b2) Gecko/20100720 Firefox/4.0b2 (.NET CLR 3.5.30729) I have a toolbar installed that I prefer to the Toolbar Search Field and therefore wanted to remove the search field from view using the Customize option. While I can do so successfully, whenever Firefox is restarted this 'preference' is not remembered and therefore the Search Field reappears. Reproducible: Always Steps to Reproduce: 1.Open Firefox 2.Right Click on an unused area of the tabs bar 3.Choose 'Customize' from the menu 4.Drag the Toolbar Search Field from the side of the awesomebar into the Customize Toolbar box. 5.Close the box, the field will have disappeared. 6.Restart Firefox Actual Results: Search Field Toolbar reappears Expected Results: Search Field Toolbar should remain hidden Build platform target i686-pc-mingw32 Build tools Compiler Version Compiler flags cl 14.00.50727.762 -TC -nologo -W3 -Gy -Fdgenerated.pdb -DNDEBUG -DTRIMMED -Zi -Zi -UDEBUG -DNDEBUG -GL -wd4624 -wd4952 -O1 cl 14.00.50727.762 -GR- -TP -nologo -Zc:wchar_t- -W3 -Gy -Fdgenerated.pdb -wd4800 -DNDEBUG -DTRIMMED -Zi -Zi -UDEBUG -DNDEBUG -GL -wd4624 -wd4952 -O1 Configure arguments --enable-application=browser --enable-update-channel=beta --enable-update-packaging --enable-jemalloc --enable-tests --enable-official-branding
Can you please test this with all extensions disabled?
Didn't work Tried the following: Restarted FF 4b2 in Safe Mode with all addons disabled and removed the Search Bar from the toolbar. Restarted the Safe Mode (addons still disabled) but still resulted in the Search Bar reappearing.
Can you also try with a fresh profile? http://support.mozilla.com/en-US/kb/Managing+profiles If that doesn't work can you please check the error console (under tools) if errors related to the search bar are reported? Also please attach a screenshot.
Using a new profile does solve this issue.
Ok, so please move the localstore.rdf file from within your profile into another folder and start Firefox. Does this help? If yes, please attach this file to this bug report. Thanks.
Moving the localstore.rdf does not solve the issue
Does resetting the toolbars under Customize help?
No
So please make a backup of the profile and while firefox is closed remove file by file from the profile until the problem is fixed. That would give us an idea which file is causing this problem. Please note that most files get recreated when you start firefox. So keep a copy separate and replace the whole testing profile.
I also get this error with FF4 beta8 I have google toolbar installed, and I have removed ALL search engines from the "default search form". Every time I restart firefox the default search form re-appears. Windows 7 32bit starter edition I'll look at what steps you want us to take tomorrow, it's a bit late tonight!
This bug could be related to bug 554279. Can one of you please run the latest nightly build of Firefox and test those steps again? http://ftp.mozilla.org/pub/mozilla.org/firefox/nightly/latest-mozilla-central/
I am now running the latest nightly 2011-01-03. The return of the search bar has not happened yet. I've opened and closed FF about 4 times now. As the week goes by I'll let you know if it does fix this issue for me. For me it did seem random, about every 3 times I opened FF it would reappear.
Please disable the Google Toolbar extension for those tests, just to make sure it doesn't have an influence. Beside that you can also test in a fresh profile. See comment 3.
This whole area has changed considerably. Marking INCOMPLETE.
Status: UNCONFIRMED → RESOLVED
Closed: 7 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.