Closed Bug 186566 Opened 23 years ago Closed 21 years ago

Mozilla deleted my cookies.

Categories

(Core :: Networking: Cookies, defect)

Product:
Core
Component:
Networking: Cookies
Platform:
x86
Windows 98
Type:
defect
Priority:
Not set
Severity:
critical

Tracking

()

Status:
RESOLVED WORKSFORME

People

(Reporter: wellander2, Assigned: morse)

Details

User-Agent: Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.0.1) Gecko/20020826 Build Identifier: Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.0.1) Gecko/20020826 Hi, When I installed this build of mozilla it deleted all of my cookies form my profile. I also use mozilla 1.3 aplha and it can not find my cookies eaither and I did not delete them and I amm upset about this.I checked my profile to see if they are still there and they are not. Reproducible: Always Steps to Reproduce: 1.Download and install this build 2.It deletes the cookies. 3. Actual Results: The same. Expected Results: Not deleted my important cookies. It is critical because I LOST DATA. And I am UPSET about it but I an getting over it very fast.
Do you mean that this build deleted your cookies : Gecko/20020826 ?
>I am sorry maybe I was not very clear. >Yes this build deleted all of my cookies. -> invalid, build is too old. We accept only bug reports from the latest milestone
Status: UNCONFIRMED → RESOLVED
Closed: 23 years ago
Resolution: --- → INVALID
verifiying. please answer in the textfield here, NOT via mail
Status: RESOLVED → VERIFIED
REOPEN: I'd like to at least isolate the cause. If there is something new going on w/ the installer, it could be worth checking out. What build were you using when cookies last worked? Do cookies work okay now?
Status: VERIFIED → UNCONFIRMED
Resolution: INVALID → ---
Benc: The installer doesn't do anything with the cookies. They are in the profile and the installer never touches the profile.
I'm willing to take the problem description at face value, which means we should try to find the cause. If it isn't the installer, then perhaps one version reading the cookies caused a formating problem for the other version? I know that people say "this isn't supported", but there are too many different products being developed on different branches these days, and profiling does not have version checking yet, so if we can figure out the cause, we should find out what is going on.
benc: are you able to reproduce this bug?
suresh: I'm not the QA on this bug. I'm just saying that we often dismiss problem reports about bad profiles that we should analyze. I think the reporter can provide enough detail about which versions are involved for someone to attempt to reproduce it.
Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.3) Gecko/20030312 For years, I have been using a backup cookie file to store essential cookies (like login for NYTimes; use a batch process to restore the file to all working browsers after online sessions). Saves an awful lot of work managing stuff. All versions of Mozilla up to this one -- which I downloaded and installed today -- have not messed with the file. The polite behavior of previous versions has been destroyed by this download. The problem seems to translate to all additional installed test versions of Mozilla and Netscape (based on the Gecko engine -- no destructive behavior has filtered back to Netscape 4x versions). Very bizarre bug. Hope you can fix it. My guess is, I'll have to uninstall 1.3 entirely, wipe out all the directories and profiles and go back to 1.2.1. Best regards, John Kratz
John: can you be a little more specific? What exactly did 1.3 do - delete your cookies on installation, or modify the cookie file somehow? which file did it mess with? your backup one, or your normal one? Hopefully we can track down the problem. btw, benc, did you get anywhere with figuring out the cause of the original reporter's bug? installer troubles?
John Kratz: What does you batch file do? Does it overwrite cookies.txt while mozilla is still running? In that case, the batch file is broken. Never touch the profile by hand while mozilla is still running. Bryan: Did the cookies never appear after installing the new build? And was that after installing 1.0.1 or 1.3a?
Bryan: Did the cookies never appear after installing the new build? No they did not. And was that after installing 1.0.1 or 1.3a? Yes it was.
Bryan: Did the cookies never appear after installing the new build? No they did not. And was that after installing 1.0.1 or 1.3a? Yes it was.
jkratz: can you respond to previous comments? without more detailed info, there's not much we can do here. thx!
Sorry to have been away for so long. 1) "Unconfirmed" Bugs. I found three posts about the untoward "cookie delete" problem on Usenet. Further, there was the original post here, and there was my supplemental post, which totals five. One should take the attitude that bug posts are like fleas. If you see one, you have millions. "Unconfirmed" might be inaccurate. 2) I uninstalled Mozilla 1.3 entirely and reinstalled 1.2. The bug persisted until I deleted the XUL.mfl file in the profile directory. Then the cookie bug disappeared. 3) With 1.4 beta version, the bug has not reappeared. I sense for the 1.4 versions this bug has been fixed. 4) Of course the batch file does not rewrite the cookie file while Mozilla is still running. 5) What had happened with all versions 1.3 I played with was every time I started the browser afresh, the cookies.txt file in the profile directory was wiped clean. That seems to have been the gist of all the posts I read on all the various sources. Best Regards, John Kratz
thanks for the reply... to respond: > 1) "Unconfirmed" Bugs. > I found three posts about the untoward "cookie delete" problem on Usenet. > Further, there was the original post here, and there was my supplemental post, > which totals five. One should take the attitude that bug posts are like > fleas. If you see one, you have millions. "Unconfirmed" might be inaccurate. possibly, but there's simply nothing we can do unless we have the details required to fix it - so serious bug or not, accurate info is important. > 5) What had happened with all versions 1.3 I played with was every time I > started the browser afresh, the cookies.txt file in the profile directory was > wiped clean. That seems to have been the gist of all the posts I read on all > the various sources. okay - can you test this further? if you could determine whether it happens _every_ time (regardless of the contents of the cookie file) that would be really helpful. for instance, the file may be corrupted by some cookie, which causes the file read to be aborted. things to try: 1) start the browser to a blank page (about:blank) and see if the file still gets wiped. or does it only occur when starting up to a page that sets a cookie? 2) create a new profile, and see if this is affected. try to determine if it occurs consistently, regardless of sites visited/cookies set, or if it might be due to a specific cookie. of course, if 1.4 works for you, that's great - but it'd still be nice to figure out what's going on here ;)
have we had any reports of this since June? With all of the changes in the backend, if there were a bug, it might no longer exist...
Hi, It is fixed now. Mark as invalid please.
-> wfm
Status: UNCONFIRMED → RESOLVED
Closed: 23 years ago → 21 years ago
Resolution: --- → WORKSFORME
Hi, Good.
You need to log in before you can comment on or make changes to this bug.