Closed Bug 583557 Opened 14 years ago Closed 14 years ago

Cookies are reset every time Firefox is closed.

Categories

(Firefox :: General, defect)

x86_64
Windows 7
defect
Not set
normal

Tracking

()

RESOLVED FIXED

People

(Reporter: traediras, Assigned: dwitte)

References

Details

Attachments

(1 file)

User-Agent:       Mozilla/5.0 (Windows; Windows NT 6.1; WOW64; rv:2.0b3pre) Gecko/20100731 Minefield/4.0b3pre
Build Identifier: Mozilla/5.0 (Windows; Windows NT 6.1; WOW64; rv:2.0b3pre) Gecko/20100731 Minefield/4.0b3pre

Whenever I quit Firefox then execute it again, all my cookies appear to be reset. I've checked the options for handling cookies and I've made sure that the browser does not automatically delete them upon being shut down, however the problem still persists, and I have to log into sites once again.

Reproducible: Always

Steps to Reproduce:
1.Open Firefox.
2.Login to any site that requires user login.
3.Quit Firefox.
4.Reopen Firefox and go to the sites that you are logged in at and check if you are still logged in.
Actual Results:  
I was logged out of any sites I was logged in to.

Expected Results:  
Firefox should have kept me logged into the sites that I had logged in to, as it had been configured to keep cookies until they expired.

about:buildconfig
Source

Built from http://hg.mozilla.org/mozilla-central/rev/f73e5032cfad
Build platform
target
i686-pc-mingw32
Build tools
Compiler 	Version 	Compiler flags
cl 	14.00.50727.762 	-TC -nologo -W3 -Gy -Fdgenerated.pdb -DNDEBUG -DTRIMMED -Zi -Zi -UDEBUG -DNDEBUG -GL -wd4624 -wd4952 -O1
cl 	14.00.50727.762 	-GR- -TP -nologo -Zc:wchar_t- -W3 -Gy -Fdgenerated.pdb -wd4800 -DNDEBUG -DTRIMMED -Zi -Zi -UDEBUG -DNDEBUG -GL -wd4624 -wd4952 -O1
Configure arguments

--enable-application=browser --enable-update-channel=nightly --enable-update-packaging --enable-jemalloc --enable-tests
Check if you have Permanent Browsing mode enabled. You can find it under preferences > privacy.
Group: core-security
That's Permanent Private Browsing mode - you're always in private mode, which means that no cookies will ever be saved.
(In reply to comment #1)
> Check if you have Permanent Browsing mode enabled. You can find it under
> preferences > privacy.

(In reply to comment #2)
> That's Permanent Private Browsing mode - you're always in private mode, which
> means that no cookies will ever be saved.

I've got Permanent Private Browsing mode off, never had any need to turn it on.

Interestingly, I can open up the latest Namoroka (FF3.6.9b) build and I'm still logged into anything that I was previously logged in to.
Check browser.privatebrowsing.autostart and browser.privatebrowsing.dont_prompt_on_enter in about:config. If you don't have anything confidential in about:support, save it to a file and attach it here.

I had a similar situation a while back where permanent private browsing mode was set (I don't know how, it wasn't intentional). Checking the prefs in the UI and in about:config fixed it for me then.
This also might be caused by bug 572223, which seems to have caused a few regressions.
(In reply to comment #3)
> Interestingly, I can open up the latest Namoroka (FF3.6.9b) build and I'm still
> logged into anything that I was previously logged in to.

And this is true using the same profile as your nightly build? Can you test the following:

1) Delete your cookies.sqlite file in your profile directory.
2) Browse using your nightly build.
3) Close the browser.
4) Browse using your Namoroka build on the same profile.

Are you still logged in at step 4)?

(Note: please test this on your current nightly build, not tonight's nightly -- the changes in bug 572223 have been backed out.)
(In reply to comment #6)
> (In reply to comment #3)
> > Interestingly, I can open up the latest Namoroka (FF3.6.9b) build and I'm still
> > logged into anything that I was previously logged in to.
> 
> And this is true using the same profile as your nightly build? Can you test the
> following:
> 
> 1) Delete your cookies.sqlite file in your profile directory.
> 2) Browse using your nightly build.
> 3) Close the browser.
> 4) Browse using your Namoroka build on the same profile.
> 
> Are you still logged in at step 4)?
> 
> (Note: please test this on your current nightly build, not tonight's nightly --
> the changes in bug 572223 have been backed out.)

Yes, I am using the same profile for all the builds. I've followed your steps and I am still logged in when browsing using the Namoroka build.

This kind of thing wasn't happenening in the Minefield 4.0b2 builds, so it seems that it might just be confined to the Minefield 4.0b3 builds.


(In reply to comment #4)
> Check browser.privatebrowsing.autostart and
> browser.privatebrowsing.dont_prompt_on_enter in about:config. If you don't have
> anything confidential in about:support, save it to a file and attach it here.
> 
> I had a similar situation a while back where permanent private browsing mode
> was set (I don't know how, it wasn't intentional). Checking the prefs in the UI
> and in about:config fixed it for me then.

Both were set to false when I checked about:config.
This is most likely fixed per bug 572223. Please reopen if you still see issues with tonight's nightly.
Assignee: nobody → dwitte
Status: UNCONFIRMED → RESOLVED
Closed: 14 years ago
Resolution: --- → FIXED
Depends on: 572223
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: