Preferences not saved: Difference between revisions

From MozillaZine Knowledge Base
Jump to navigationJump to search
(consolidated first 2 sections, updated link, added Category:Configuration" and "see also" link to related article)
Line 1: Line 1:
This article deals with Firefox or Mozilla Suite not saving any changes made to options or preference settings after you restart the application.  If only Firefox toolbar customizations are not being saved, see [[Corrupt localstore.rdf |this article]].
This article deals with Firefox or Mozilla Suite not saving any changes made to options or preference settings after you restart the application.  If only Firefox toolbar customizations are not being saved, see [[Corrupt localstore.rdf |this article]].  


==Read-only or locked preference file==
==Read-only or locked preference file==
The inability to save any preference changes can be caused by having a read-only or locked [[prefs.js file]] or "prefs.js.moztmp" file in the [[profile folder]].  You may receive an error similar to "Failed to save the preferences file.  Any preference changes will be lost at the end of the session"  [http://forums.mozillazine.org/viewtopic.php?t=455989].  You may also find multiple files named "prefs-n.js" (where n is a number) in the profile folder.  Check the file properties of the prefs.js file (and  "prefs.js.moztmp" file, if found) and make sure that the "read-only" attribute is not set.  You can also delete any "prefs-n.js copies.  See the article, [[Multiple profile files created]] for more information.
The inability to save any preference changes can be caused by having a read-only or locked [[prefs.js file]] or "prefs.js.moztmp" file in the [[profile folder]].  You may receive an error similar to "Failed to save the preferences file.  Any preference changes will be lost at the end of the session"  [http://forums.mozillazine.org/viewtopic.php?t=455989].  You may also find multiple files named "prefs-<n>.js" (where <n> is a number) in the profile folder.  Check the file properties of the prefs.js file (and  "prefs.js.moztmp" file, if found) and make sure that the "read-only" attribute is not set.  You can also delete any "prefs-<n>.js" file copies.   


==Dell Network Assistant==
Note that other software such as Dell Network Assistant may be causing the problem by locking or "protecting" the preference file. If you have this program, try disabling or uninstalling it [http://forums.mozillazine.org/viewtopic.php?t=461093].  See [[Multiple profile files created]] for more information about locked or multiple files in the profile. 
Dell Network Assistant may also cause this problem. If you have this program, try uninstalling it.[http://forums.mozillazine.org/viewtopic.php?t=461093]


== User.js file locks certain preferences ==
== User.js file locks certain preferences ==
If you are able to change some preference settings but not others,  look for a [[user.js file]] in your [[profile folder]] (Windows users, read [[Profile_folder#For_Windows_users |this]]).  The user.js file does not exist by default; it is created by users and, in a few  cases, by [[Resetting_preferences#Software_that_changes_preference_settings |some software programs]], so that certain settings get written back to the [[prefs.js file]] each time you restart Firefox or Mozilla Suite.  If you find a user.js file, either remove it from the profile folder or edit the file to remove any unwanted settings.  See the article [[Resetting preferences]] for more information.
If you are able to change some preference settings but not others,  look for a [[user.js file]] in your [[profile folder]] (Windows users, read [[Finding the profile folder on Windows |this]] for help finding it).  The user.js file does not exist by default; it is created by users and, in a few  cases, by [[Resetting_preferences#Software_that_changes_preference_settings |some software programs]], so that certain settings get written back to the [[prefs.js file]] each time you restart Firefox or Mozilla Suite.  If you find a user.js file, either remove it from the profile folder or edit the file to remove any unwanted settings.  See the [[Resetting preferences]] for more information.


==See also==
*[[Locking preferences]]


[[Category:Configuration]]
[[Category:Issues (Firefox)]]
[[Category:Issues (Firefox)]]
[[Category:Issues (Mozilla Suite)]]
[[Category:Issues (Mozilla Suite)]]

Revision as of 14:04, 6 December 2007

This article deals with Firefox or Mozilla Suite not saving any changes made to options or preference settings after you restart the application. If only Firefox toolbar customizations are not being saved, see this article.

Read-only or locked preference file

The inability to save any preference changes can be caused by having a read-only or locked prefs.js file or "prefs.js.moztmp" file in the profile folder. You may receive an error similar to "Failed to save the preferences file. Any preference changes will be lost at the end of the session" [1]. You may also find multiple files named "prefs-<n>.js" (where <n> is a number) in the profile folder. Check the file properties of the prefs.js file (and "prefs.js.moztmp" file, if found) and make sure that the "read-only" attribute is not set. You can also delete any "prefs-<n>.js" file copies.

Note that other software such as Dell Network Assistant may be causing the problem by locking or "protecting" the preference file. If you have this program, try disabling or uninstalling it [2]. See Multiple profile files created for more information about locked or multiple files in the profile.

User.js file locks certain preferences

If you are able to change some preference settings but not others, look for a user.js file in your profile folder (Windows users, read this for help finding it). The user.js file does not exist by default; it is created by users and, in a few cases, by some software programs, so that certain settings get written back to the prefs.js file each time you restart Firefox or Mozilla Suite. If you find a user.js file, either remove it from the profile folder or edit the file to remove any unwanted settings. See the Resetting preferences for more information.

See also