1508149 - Upgrade to Firefox 60 from 52 lost all saved passwords

Status: RESOLVED DUPLICATE of bug 1505038

(Core :: Security: PSM, defect)

Description

[Tim McCormack]

User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Firefox/52.0

Steps to reproduce:

Launch Firefox ESR 60.3.0 when ~/.mozilla/ contained profiles last touched by Firefox ESR 52.9.0

This is on Debian 9 (Stretch).


Actual results:

- Main profile came up fine (session restored OK)
- I couldn't log into anything
- Preferences -> Saved Logins shows nothing


Expected results:

- All saved passwords preserved and available for use

Comment 1

[Adrian Florinescu [:aflorinescu]]

Upgrading between 52.0.2 20170323110425 and 60.3.0esr 20181017185317 on both Ubuntu 16.04 and Debian 9.3 x64 with facebook, google passwords offered no results in my attempts to reproduce this scenario. 

However there are known issues related to the upgrade from 52esr to 60.3.0ESR. Please see bug 1505038 and bug 1496736. 

I would guess this bug might be a duplicate after bug 1496736, although that bug seems to be localized on redhat, but it's not unlikely to be more widely spread to other distros. 

I'm also uncertain though why the results when upgrading are intermittent for you as stated in https://bugzilla.mozilla.org/show_bug.cgi?id=1508148#c2. Could you perhaps test an "upgrade" from 52esr to 64beta or 65Nightly on a restored test profile? (read "upgrade" like just running the same profile with 52 then with Nightly65 - you can get it from here - https://download.mozilla.org/?product=firefox-nightly-latest-ssl&os=linux64&lang=en-US) - where I would expect that the password manager would function properly.

Comment 2

[Tim McCormack]

Yes, I think tomorrow I'll have some time when I can retrieve a 52.9.0 profile backup and try to repro with 64 or 65.

Comment 3

[Dana Keeler (she/her) (use needinfo) [:keeler] (on leave)]

Any luck?

Comment 4

[Tim McCormack]

I'm having difficulty reproducing because the Firefox 52.9.0 extracted from tarball keeps *updating* itself, and I therefore accidentally upgrade the profiles before I'm ready.

I'll need to do another restore from backup to get back to a pre-repro state. Maybe this weekend.

Comment 5

[Tim McCormack]

OK, I was able to grab some time.

I was *not* able to reproduce the failure with 60.3.0 a third time. I tried with 65 (64 just crashed) and was not able to repro, but I don't know how meaningful that is.

It seems that there's definitely an ESR -> ESR upgrade issue, but it's not clear what the precise conditions are. :-/

Comment 6

[Dana Keeler (she/her) (use needinfo) [:keeler] (on leave)]

Let's just duplicate this to bug 1505038 then.