2018.04.26: Password Manager problems, but only with new profile Topic is solved

[coffeebreak]

There are some problems with Basilisk-20180426's Password Manager that seem to only occur when a fresh, new profile is in use - where the Password Manager has not inherited any passwords/exceptions from earlier Basilisk versions:

1. The password manager thinks that a master password is in use, even though none was ever created.

2. Passwords created in Basilisk-20180426 are not saved - unless some passwords from earlier times (older Basilisk) are already present. (They might at first seem to be saved, if the browser has not yet been restarted)

To reproduce:

• Open Basilisk-20180426 in a new profile.
• Go to Preferences > Security / "Use a master password" (checkbox).
• Observe that the checkbox is unchecked (the default).
• Then either:
  a) Restart the browser twice; or
  b) Save any password, then restart the browser once.

The checkbox for "Use a master password" is now checked.
And the browser asks for a master password to be entered in the places where it would normally ask if a master password actually existed.

The password can be reset (chrome://pippki/content/resetpassword.xul) -
but after two restarts the problem is back.

[coffeebreak]

This is fixed with the 2018.04.27 update.