476369 - after upgrade to seamonkey 1.1.14, all mail disappeared

Status: RESOLVED INVALID

(SeaMonkey :: MailNews: Account Configuration, defect)

Description

[Randy Risher]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.19) Gecko/20081204 SeaMonkey/1.1.14
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.19) Gecko/20081204 SeaMonkey/1.1.14

V1.1.14 upgrade lost email access totally.
All accounts disappeared.
All folders gone.

Folders remained intact.
Link to folders disappeared.

Reproducible: Didn't try

Steps to Reproduce:
1.
2.
3.

Comment 1

[Frank Wein [:mcsmurf]]

What version did you upgrade from? And what do you mean with
"All folders gone.

Folders remained intact." ?
You mean that the folders with mail in it still exist on your disk?

Comment 2

[Randy Risher]

Upgraded from 1.1.13
Directory structure was 
6xkgymix.slt\Mail\account1, account2,... etc

This was about the 10th upgrade seamonkey has asked me to do and the first that lost the linkage to the mail directory (folder).

Needless to say I was fortunate enough to be one who backs up and I restore the prefs.js file as support FAQ suggested.

I am reporting not because I needed help fixing it, but rather to draw attention that it happened...

Thing is: now I am leery of doing the SeaMonkey upgrades and may switch to Firefox & Thunderbird.

Comment 3

[rsx11m]

There are various reports about profiles occasionally "disappearing" after updates or system crashes, see bug 392956 for another report. 

> Thing is: now I am leery of doing the SeaMonkey upgrades and may switch to
> Firefox & Thunderbird.

Thunderbird is equally affected, this is shared code anyway, thus switching wouldn't help. There are several possible reasons why the profile is no longer recognized on startup, some theories presented in the bug report I referred you to (which is on Thunderbird, by the way). Thus, apparently you've hit one of those cases...

Comment 4

[Randy Risher]

Thanks for the heads up on Thunderbird. Seems that what happened was exactly that - the loss or corruption of the prefs.js file as restoring from backup did fix the problem.  Appreciate your help - r

Comment 5

[rsx11m]

Adding this as another case to tracking bug 123929 on profile corruption.

Comment 6

[Wayne Mery (:wsmwk)]

so, only prefs.js was lost?

Comment 7

[Ian Neal]

As this from 1.1 branch and no longer supported -> INVALID