Bug 133673 – preferences can not be saved

Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.

Bug 133673 - preferences can not be saved

Summary:	preferences can not be saved

Status:	CLOSED DUPLICATE of bug 133503

Aliases:	None

Product:	Fedora
Classification:	Fedora
Component:	firefox (Show other bugs)
Sub Component:
Version:	3
Hardware:	athlon Linux

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

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	2004-09-25 22:20 EDT by Huan Ma
Modified:	2007-11-30 17:10 EST (History)
CC List:	1 user (show)

See Also:
Fixed In Version:
Doc Type:	Bug Fix
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:	2006-02-21 14:05:54 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 Huan Ma 2004-09-25 22:20:08 EDT

Description of problem:
When the preferences are changed, they can not be saved. After "OK"
button is clicked, an error message pops up with "Failed to save the
preferences file. Any preference changes will be lost at the end of
this session."

Version-Release number of selected component (if applicable):
1.0PR

How reproducible:
As in description. Every time.

Steps to Reproduce:
1. open preferences window
2. change some options
3. click "OK"
  
Actual results:
Error window: "Failed to save the preferences file. Any preference
changes will be lost at the end of this session."

Expected results:
changes are saved successfully.

Additional info:

Comment 1 Warren Togami 2004-09-25 23:34:11 EDT


*** This bug has been marked as a duplicate of 133503 ***

Comment 2 Red Hat Bugzilla 2006-02-21 14:05:54 EST

Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.

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