Red Hat Bugzilla – Bug 155650
Default seach engine preference replaced after upgrade
Last modified: 2018-04-11 03:06:39 EDT
Description of problem:
After upgrading from mozilla-1.7.6-1.3.2 to mozilla-1.7.7-1.3.1, search
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. In mozilla, choose Google as default search engine using
2. Upgrade to mozilla-1.7.7-1.3.1 from a previous release.
3. Run moz and click Edit->Preferences->Navigator->Internet Search
"Ask Jeeves" is shown as the default search engine.
The default search engine preference chosen before the upgrade should persist.
(I.e., "Google" should appear as the default engine in this case.)
Also, searches initiated by typing the the address bar and clicking "Search
for..." drop-down should continue to work.
On top of the default appearing to be changed, searches initiated by typing
keywords in the address bar and then clicking the "Search for..." drop-down do
*nothing at all*. Until the user updates his default search engine preference.
Additional additional info:
This problem has occurred with each of several mozilla upgrades over the past
year or so, IIRC.
Fedora Core 3 is now maintained by the Fedora Legacy project for security
updates only. If this problem is a security issue, please reopen and
reassign to the Fedora Legacy product. If it is not a security issue and
hasn't been resolved in the current FC5 updates or in the FC6 test
release, reopen and change the version to match.
Distribution against which this bug was reported is no longer supported; could
you please reproduce this with the updated version of the currently supported
distribution (Fedora Core 6, or Fedora 7, or Rawhide)? If this issue turns out
to still be reproducible, please let us know in this bug report. If after a
month's time we have not heard back from you, we will have to close this bug as
Setting status to NEEDINFO, and awaiting information from the reporter.
Thanks in advance.
We haven't got any reply to the last question about reproducability of the bug
with Fedora Core 6, Fedora 7, or Fedora devel. Mass closing this bug, so if you
have new information that would help us fix this bug, please reopen it with the