Bug 160174 – mozilla forgets smart search setting on upgrade

Bug 160174 - mozilla forgets smart search setting on upgrade

Summary:	mozilla forgets smart search setting on upgrade

Status:	CLOSED CANTFIX

Aliases:	None

Product:	Fedora
Classification:	Fedora
Component:	mozilla (Show other bugs)
Sub Component:
Version:	rawhide
Hardware:	All Linux

Priority	medium Severity medium
Target Milestone:	---
Target Release:	---
Assigned To:	Christopher Aillon
QA Contact:	Ben Levenson
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	2005-06-12 14:44 EDT by Jonathan Kamens
Modified:	2008-02-08 11:17 EST (History)
CC List:	0 users

See Also:
Fixed In Version:
Doc Type:	Bug Fix
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:	2008-02-08 11:17:37 EST
Type:	---
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Groups: None (edit)

Description Jonathan Kamens 2005-06-12 14:44:44 EDT

I have mozilla configured to use Mozilla for searching.  Every single time I 
upgrade to a new mozilla RPM, it forgets this setting and I have to re-enter 
it.  Furthermore, it gets into some weird state where even though the 
preferences dialog claims that it's configured to use Ask Jeeves for 
searching, if I actually type a search query into my Address bar and click the 
down arrow and hit enter to search, it doesn't work.

Comment 1 Matěj Cepl 2008-02-08 11:17:37 EST

Since this bugzilla report was filed, we have seriously upgraded Gecko-related
packages in Rawhide, which may have resolved this issue. Users who have
experienced this problem are encouraged to upgrade their system to the latest
version of their distribution available.

Closing this bug as CANTFIX. Please, reopen, if this bug is still reproducable
on the latest update of your distribution.

[This is mass-closing of bugs which seem to be too old and irrelevant anymore;
we are sorry, if we are closing your bug in mistake; please, don't hesitate to
reopen, if it is still alive issue.]

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