Bug 155650 - Default seach engine preference replaced after upgrade
Default seach engine preference replaced after upgrade
Status: CLOSED INSUFFICIENT_DATA
Product: Fedora
Classification: Fedora
Component: mozilla (Show other bugs)
3
All Linux
medium Severity medium
: ---
: ---
Assigned To: Christopher Aillon
Ben Levenson
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2005-04-22 03:43 EDT by Jack Spaar
Modified: 2007-11-30 17:11 EST (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2007-08-28 10:56:23 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:


Attachments (Terms of Use)

  None (edit)
Description Jack Spaar 2005-04-22 03:43:30 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):


How reproducible:
Always

Steps to Reproduce:
1. In mozilla, choose Google as default search engine using
Edit->Preferences->Navigator->Internet Search
2. Upgrade to mozilla-1.7.7-1.3.1 from a previous release.
3. Run moz and click Edit->Preferences->Navigator->Internet Search
  
Actual results:
"Ask Jeeves" is shown as the default search engine.


Expected results:
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.

Additional info:
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.
Comment 1 Matthew Miller 2006-07-10 17:42:57 EDT
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.

Thank you!
Comment 2 Matěj Cepl 2007-07-18 13:23:57 EDT
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
CANTFIX.

Setting status to NEEDINFO, and awaiting information from the reporter.

Thanks in advance.
Comment 3 Matěj Cepl 2007-08-28 10:56:23 EDT
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
additional information.

Note You need to log in before you can comment on or make changes to this bug.