Closed Bug 36310 Opened 26 years ago Closed 26 years ago

added second news server account not visible after restart

Categories

(SeaMonkey :: MailNews: Account Configuration, defect, P3)

Product:
SeaMonkey
Component:
MailNews: Account Configuration
Platform:
x86
Windows NT
Type:
defect

Tracking

(Not tracked)

Status:
VERIFIED FIXED

People

(Reporter: Marko.Macek, Assigned: alecf)

Details

If I create a new newsgroup account it seems to work fine until restart of mozilla when the server is not visible anymore. I have to manually edit user.js to make it stay. user_pref("mail.accountmanager.accounts", ... The accound only seems to be listed in prefs.js??? Should I remove my profile ?
Build id: 2000041808 (happened already in previous builds)
I wonder if remotely related to http://bugzilla.mozilla.org/show_bug.cgi?id=34408. This bug sounds familiar to me. cc: nbaca and huang.
QA Contact: lchiang → huang
that's odd. so you mean the account added to the prefs (you have entries like mail.servers.<serverid>.hostname and such) but not to that one pref, mail.accountmanager.accounts?
alecf: yes. The entries you mention are added to "prefs.js", but I have to manually add the account to the list in "user.js" to make the accound appear after restart. (Why the two files. Perhaps the confusion is there?) I looked at bug 34408 but it seems I have the opposite problem. Everything works fine (2 news servers + local folders) until I restart when I lose the second server. (I then manually added the account and that fixed it).
there's your problem! move any prefs from user.js into prefs.js and then delete user.js we had one build a few weeks ago that created a user.js accidentally, and then future uses get horked.
I cannot reproduce this problem by using today's 04-19-09-M16 commercial build: I can added second news server and subscribe newsgroup successfully.
marko - did you try what alecf suggested? I'll leave this bug unconfirmed until you do so with your response since we had problems that may cause what you were seeing and those problems have been fixed. Thanks.
Yes, it worked. Marking FIXED (or should that be INVALID?)
Status: UNCONFIRMED → RESOLVED
Closed: 26 years ago
Resolution: --- → FIXED
Verified 07-06-09-M17 commercial build. This was fixed and verified no problem anymore.
Status: RESOLVED → VERIFIED
Product: Browser → Seamonkey
You need to log in before you can comment on or make changes to this bug.