This could be installer bug rather than mail front end bug but not sure. Using current commercial branch (20020627 or 20020628) on XP, win2k. Mozilla/5.0 (Windows; U; WinNT4.0; en-US; rv:1.0.0) Gecko/20020627 If you install the current branch over previous 6.2,6.22, or 6.23 build, start Messenger only, and then go to Edit|Preferences|Mail&Newsgroup prefs you will see blank pref window. This is the only case when it comes up blank. If you go back to Edit|Preferences|Mail&Newsgroup again, it displays the prefs fine. Start browser, go to Edit|Preferences|Mail&Newsgroup - ok start messenger, go to edit|Mail&Newsgroup Account settings, then go to Edit|Preferences|Mail&Newsgroup - ok Tried installing current branch over 6.1 and I don't see this problem. steps to reproduce: 1.Create a mail account in 6.2,6.22, or 6.23 2.Login to account. 3.Quit 4.Install current branch over same directory 5.Start Messenger only -via run menu nscpe.exe -mail -via short cut on desktop -via start menu in windows 6.Don't need to login at the prompt but you can if you want 7.Go to Edit|Preferences result: it takes you to 1st panel of Mail&Newsgroups and its blank expected: to not be blank If I go back to Mail&Newsgroup prefs, it's not blank. If I quit, start browser first, then messenger, it's not blank. It only occurs when starting mail by itself and you go to Edit|Preferences|Mail&Newsgroup the very first time. All subsequent times it's fine.

just adding another note that I now see this when I start browser, then start messenger, then go to Edit|Preferences in Messenter.

Reporter: Is this still an issue with a current Mozilla build?

MASS-CHANGE: This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state. If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way. If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar). If no action happens within the next few months, we move this bug report to an EXPIRED state. Query tag for this change: mass-UNCONFIRM-20090614

certainly wfm these days.