Firefox 112.0 logs out all tabs on exit
My Firefox recently updated itself to version 112.0 - since then, when I close all its windows and then run FF again, on all websites opened in tabs (e.g. Facebook, Google Search etc.) I am logged off. In previous FF versions, my logged-in status was preserved between individual FF runs. Firefox not only logs me out of all sites, but also logs me out of the LastPass extension, which also stayed logged in in previous Firefox versions. Anyone knows what is going on? I dont want to have to relogin to all sites each time...
If this problem was caused by the future-dated cookies bug -- you can check the Manage Data dialog on the Settings page and observe whether the cookies were "Last Used" many years in the future -- there is an update for that:Read this answer in context 👍 1
All Replies (11)
Check your settings on the Privacy page. The update may have changed them. Others have reported the same issue.
I dont see anything wrong on Privacy page settings. The update apparently changed something not so obvious. How can the developers let out something like this? :-/
Version 112 certainly seems to have caused some issues. You can load the release notes on this link : https://www.mozilla.org/en-US/firefox/releases/
- /questions/1410735 Firefox update from 111.0.1 to 112 set the dates of most cookies into the far future and keeps doing it
Before this stupid bug will be fixed, I can recommend using Waterfox browser instead - it is compatible and can import your extensions and bookmarks via Firefox account.
You should be able to fix this by deleting cookies.sqlite in the Firefox profile folder to make Firefox create a new database.
Thanks, but before I will start to re-create the cookies database, I want to be sure that the bug is fixed and Firefox will not corrupt the database again.
If this problem was caused by the future-dated cookies bug -- you can check the Manage Data dialog on the Settings page and observe whether the cookies were "Last Used" many years in the future -- there is an update for that:
Yes, it seems to be fixed by 112.0.1. Thanks all for advices :) However, my trust in Firefox QA is quite shaken.
You can set Firefox to notify you of updates instead of auto-installing, and then "snooze" the notification for a couple of days to reduce bug risk. (On the Settings page, enter update in the tiny search box.)
In this case, I don't think anyone has figured out why some users were affected by this. Was it some specific site in their cookies? Lurking file corruption? Bad luck??
Yes, after this experience, I have turned autoupdate off. Do you think that some users had their cookies intact in this case?