204054 - Changes done in Account Manager NOT saved to prefs.js - Need to hand-edit for them to work

Status: RESOLVED EXPIRED

(SeaMonkey :: MailNews: Account Configuration, defect)

Description

[F. Javier Jarava]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.3a; MultiZilla v1.4.0.1) Gecko/20030315
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.3a; MultiZilla v1.4.0.1) Gecko/20030315

When doing changes to the different accounts in the Account Manager, such as
turning off HTML mail composing, or auto-check for mail, or trying to use SSL
for the connection (i.e, any change from the "default" settings that the account
creation wizzard sets), the changes don't "remain". Closing Mail & Groups and
opening again, the changes are undone. Moreover, after closing all mozilla
windows and the QuickStart icon, and looking at prefs.js, the changes are not there.

The only way to "get" the changes into the system is closing _all_ mozilla
(including QuickStart), hand-edit prefs.js to add the changes, and restart
Mozilla (BTW, is there any good docs on the different settings for Prefs.js?).

I've been able to reproduce this problem on two different computers (work &
home), running W2K PRO(ES) and W2K SRV(EN).

Reproducible: Always

Steps to Reproduce:
1. Open account manager with several accounts created
2. Edit some account prefs (for example, mail check interval, or HTML formatting)
3. Press OK, close Mail & News. Reopen Mail & News, open Account manager -
Changes are undone

Actual Results:  
Things (settings) were as before...

Expected Results:  
Save the new settings, and honor them..

Theme: Both with Crystal-Classic
(http://www.kdelook.org/content/show.php?content=5697) and with "Modern".

Comment 1

[WADA:World Anti-bad-Duping Agency]

Same as Bug 166912 ?

Comment 2

[Gervase Markham [:gerv]]

This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
Firefox:     http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey:   http://www.mozilla.org/projects/seamonkey/

Comment 3

[Gervase Markham [:gerv]]

This bug has been automatically resolved after a period of inactivity (see above
comment). If anyone thinks this is incorrect, they should feel free to reopen it.