226970 - lost of all stored passwords if out of disk space file truncated to zero length

Status: RESOLVED WORKSFORME

(SeaMonkey :: Passwords & Permissions, defect)

Description

[vab]

User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.6a) Gecko/20031029
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.6a) Gecko/20031029

If you are running the mozilla browser and run out of disk space, attempting
to save a new username/password pair to the password manager will result in
truncation and loss of all usernames and passwords currently stored.  

Reproducible: Always

Steps to Reproduce:
1.  fill your /home partition to 100% 0 bytes avail.
2.  tell mozilla to save a username/password web page form login
3.  exit mozilla
4.  go to a web site for which a username/password was stored (example: hotmail.com)
5.  notice that mozilla has forgotten your login information (ex: your hostmail
account name)

Actual Results:  
mozilla lost all usernames and passwords.

Expected Results:  
mozilla should have given a disk full error and not attempted to write the 
revised password database to disk.

This seems to be part of a group of problems associated with full disks across 
all platforms.  For example, mail messages to don't display when disk is full,
perfs are lost, cookies are lost, etc.  QA engineers should fill disk on all 
platfroms while running mozilla then restart and look for data loss bugs 
before 1.6b is released.

Comment 1

[Michael Lefevre]

vab: if you want to nominate a bug to block a release, you should set the flag
to "?", not "+".

Comment 2

[Asa Dotzler [:asa]]

see also bug 192425 bug 145558 and bug 145557

Comment 3

[Tony Mechelynck [:tonymec]]

No comments in over 4 years. Is anyone still seeing this bug on a recent SeaMonkey build?

(In reply to comment #2)
> see also bug 192425 bug 145558 and bug 145557
> 

Bug 145558 is "Windows", this one is "Linux". Are they different issues or should their Platform/OS be extended? The other two are FIXED by now.

Comment 4

[Andrew Hagen]

No follow-ups from people continuing to say that this is still a problem on current Seamonkey builds on Linux. Resolving WFM. 

If you are still seeing this on current Seamonkey trunk builds on Linux, please post details and re-open this bug report.