936568 - FF 26 not retaining session logins on restart or crash

Status: RESOLVED DUPLICATE of bug 950399

(Firefox :: Session Restore, defect)

Description

[David Butler]

User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:26.0) Gecko/20100101 Firefox/26.0 (Beta/Release)
Build ID: 20131028225529

Steps to reproduce:

When I restart FF 26, either from a crash, restart or quit. This began after loading latest Mac OS 10 Security Update.


Actual results:

ALL my live session logins were lost: email, Google, LinkedIn and Facebook, etc.


Expected results:

Previously all my active logins were maintained whenever I restarted for whatever reason. All the above sites responded as if I was still logged in, assuming the shutdown didn't exceed the site's timeout parameters.

Comment 1

[Loic]

Could you reset your profile and test again, please.
https://support.mozilla.org/en-US/kb/reset-firefox-easily-fix-most-problems

Comment 2

[David Butler]

(In reply to Loic from comment #1)
> Could you reset your profile and test again, please.
> https://support.mozilla.org/en-US/kb/reset-firefox-easily-fix-most-problems

I am not sure why you are asking for that. Why would that change this issue? This started, as I mentioned, after installing a MAC OS Security Update. I hadn't made any changes to Firefox. I am willing to try a reset but I would like a little more information if you could, as I have found getting my configuration back to where I like it after reset to be time-consuming. Thanks.

Comment 3

[[:Aleksej]]

You can just create a new profile (command line "-P" option).

As for resetting, it is supposed to copy the profile into the desktop folder.  But Loic, I think you suggest resetting too often.  I don't see how it's a replacement for safe mode or new profile creation.

Comment 4

[Loic]

Because safe mode is a debugging mode and can't be used as "standard" mode to use Firefox daily (I saw users asking how to quit the safe mode...).
Creating a new profile implies data loss (all private data stay in the old broken profile and the user needs to export them manually, and sometimes he doesn't know which files to export).

So resetting the current profile is the easiest way to fix some issues, it's automatic, the private data are exported and the old profile is kept.

But I agree advanced users are able to test the safe mode to debug some broken extensions/prefs or playing with new profiles without our help.

Comment 5

[[:Aleksej]]

(In reply to Loic from comment #4)
> Creating a new profile implies data loss (all private data stay in the old
> broken profile and the user needs to export them manually, and sometimes he
> doesn't know which files to export).

When creating a new profile, users know that everything is left in the old profile.

After resetting Firefox, people actually think dataloss happened, like in bug 935397.  Sometimes they don't look at the desktop, sometimes the actual desktop is not affected, see bug 921462.  And some small, unlikely, but real dataloss might actually happen: bug 921449, bug 921469.

Comment 6

[Annyella Pawlowski]

Same problem here. It's really annoying.

Comment 7

[Wayne Mery (:wsmwk)]

clarify please by "session login" you mean that the tab DOES open, but that your login status is not maintained?

And what are your results with a new, or reset profile?

Comment 8

[Annyella Pawlowski]

I've created a new profile for testing. Here are the steps:

1) Open facebook.com and login (without checking "keep me logged in")
2) Go to http://addons.mozilla.org and install a random extension that requires restarting.
3) Restart the browser.
4) All the tabs are restored, but I have to loggin on Facebook again.

Previous versions didn't have this problem. Running version 27 on Windows 8.1 64 bits right now.

Comment 9

[Wayne Mery (:wsmwk)]

I'm unsure session is correct component, but it's a start

Comment 10

[Wayne Mery (:wsmwk)]

I had something like this happen yesterday. iirc I changed no settings prior to restart. There might have been addon updates - unsure

Comment 11

[Wayne Mery (:wsmwk)]

David, the reporter seems to be gone. And I haven't seen this in a long time

Comment 12

[Tim Taubert [:ttaubert] (inactive)]

Most likely a dupe of bug 950399.