User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:18.104.22.168) Gecko/20101203 Firefox/3.6.13 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:22.214.171.124) Gecko/20101203 Firefox/3.6.13 I have attempted to remove search engines using the Manage Search Engines option. Each time I attempt to remove any or all, the system locks up! If I attempt to remove Yahoo only, the Firefox system LOCKS! Why can I not select which search engine I require as a default option as in past versions of Firefox? Reproducible: Always Steps to Reproduce: 1. As described above 2. 3. Actual Results: A LOCKED Firefox platform!!!!! Expected Results: A functioning Firefox Platform using selected search engine.
Does that also happen in safe mode with all extensions disabled? http://support.mozilla.com/en-US/kb/Safe Mode
Component: Menus → Search
QA Contact: menus → search
Version: unspecified → 3.6 Branch
THIS HAS BEEN GOING ON WITH ME TOO! Sooo irritating, it now has both the default set - why does it re add those with every damn update??!! - and now has my personal selections too, making the drop down scrollable there are co many search engines. I have emailed support several times and ways at this point and get NO RESPONSE!
I have discovered that the Manage Search Engines will not accept an OK click after I have changed the search engine order. This has persisted through a number of versions. And I have the same problem in Safe Mode (I am in that mode as I type).
I found that cleaning out my profile fixed the problem. It's like cleaning out the Augean Stables, but the browser also seems to work a little better, too.
Unfortunately, there is not enough information here to fix anything. Given that there have been many changes to related code areas (the engine order is no longer stored in an sqlite database, the manager search engine dialog no longer exists, ...) I don't think this bug is still relevant.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 3 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.