Chrome 64-bit silently fails to import passwords from Firefox 32-bit (nss3.dll won't load). |
|||||||||||||
Issue descriptionLooks like FF password storage changed again and import is broken again in Chrome 49 : https://crbug.com/510865#c13 (haven't confirmed issue myself)
,
Mar 6 2016
,
May 31 2016
,
Sep 28 2016
Issue 435153 has been merged into this issue.
,
Sep 28 2016
Still occurs with Chrome Version 53.0.2785.116 m (64-bit) and Firefox version 49.0.1 +isherman: maybe this can be addressed in the scope of issue 638977?
,
Nov 12 2016
,
Apr 24 2017
I don't think this is a problem with the format as initially mentioned. The format in the latest version of Firefox still seems identical to what firefox_importer.cc already supports. However from what I can tell, loading nss3.dll from within Chromium has started failing, which seems to be causing this issue.
,
Apr 25 2017
Interesting, perhaps chrome unintentionally blocks nss3.dll. Flipping status back to Untriaged for Windows team to investigate.
,
Apr 28 2017
Argh, or so I thought until I noticed I had 64-bit Chromium and 32-bit Firefox installed, which explains why loading the dll failed. :( Using 64-bit Firefox, importing Firefox passwords to Chromium works perfectly fine as is! From what I can tell Mozilla vends the 32-bit version of their browser as default for some reason, which might be causing this issue for some people. Pretty sure this is a non-issue at latest tip of master with Firefox 53 Can someone confirm and then close?
,
Apr 28 2017
Aaah, interesting! +wfh
,
Apr 28 2017
it might be nice to have a dialog or some kind of meaningful error message that displays what's happening here and gives advice on what to do (i.e. install Firefox 64-bit). I'm not sure I will have time to do this though.
,
Apr 28 2017
If this is not super-urgent, I might be able to take a shot at it :)
,
May 3 2017
Still reproduces. I can't get passwords to import into 64-bit Chrome (tried M58 and M60) from 32-bit Firefox (54.0b4). Flipping back to Available to get this out of the triage queue, since it doesn't seem high priority.
,
May 3 2017
That's expected though - where would the 64bit nss3.dll come from to facilitate that import? The only option here would be to bundle a 64bit version of nss3.dll (and all its dependencies) with Chrome, which doesn't sound like a great solution :(
,
May 3 2017
we can't bundle any of these DLLs. All we can do is point to a help center article or in-product information to tell the user that they need to install 64-bit firefox if they want to import bookmarks into 64-bit Chrome. It's far from ideal.
,
May 3 2017
On second thought, I'll actually take a look at this.
,
May 4 2017
,
Sep 18 2017
Assigning to pbos@ to do as a first bug.
,
Sep 19 2017
Firefox has started auto-migrating 32-bit installations on 64-bit systems (confirmed by bsep@ who just updated his 32-bit installation and got 64-bit). I couldn't install a 32-bit Firefox even when trying to download the 32-bit installer from their webpage. That being the case I think this is a disappearing population (64-bit Chrome + 32-bit Firefox) and we can WontFix it. It's not worth the engineering time or added complexity. Existing Firefox installations will be upgraded to 64-bit and Chrome should be able to upgrade from those.
,
Sep 19 2017
Cross-reference, looks like this has kicked in for some percentage of beta users: https://bugzilla.mozilla.org/show_bug.cgi?id=1274659 |
|||||||||||||
►
Sign in to add a comment |
|||||||||||||
Comment 1 by gab@chromium.org
, Mar 6 2016