Lost passwords after 29.2.0 Topic is solved

[Stevkleb]

Hi,

I have lost my passwords after upgrading to the newest version. Password stored exceptions are still listed, but my master password is disabled and the stored list is empty. It won't even allow me to set the master password now. I haven't been using any password related extensions nor any extensions that got disabled with the latest update.

Is there a way to get the data back, and what about not being able to set the master password?

[Moonchild]

Sounds like you upgraded from a much older version without going through the necessary intermediate.
Please see http://developer.palemoon.org/docs/profile-migration/

[Stevkleb]

I believe it wasn't more than 6 months old, but I can't be sure. If I understood the instructions, I should downgrade to 28.17.0?

[Moonchild]

Downgrading to 28.17.0, running the browser, to be certain checking your password store and master password being functional, then exiting and upgrading to the latest version should get you back up to speed. Although it would be better to restore your profile from a backup prior to updating instead of downgrading, I'm aware that not everyone makes regular backups of their profile (you should!) and I'm fairly certain there currently isn't any issue with downgrading to 28.17 and then back up to 29.2.

[New Tobin Paradigm]

Downgrading won't help without profile mangling cause the NEW nss store version 9 files will have been generated already preventing a migration of nss store version 8 files. One would have to remove the version 9 files THEN run the touchbase application version so that the store migration proceeds. Of course, profile mangling excludes one from implicit support and anything else is at our sufferance since they should be performing proper backups anyway. Given that the Profile Migration authoritative document exists as well as even before the recent revision to our Release Engineering Cycle.. our releases have been fairly predictable.

[Stevkleb]

Downgrading to 28.17.0, running the browser, to be certain checking your password store and master password being functional, then exiting and upgrading to the latest version should get you back up to speed. Although it would be better to restore your profile from a backup prior to updating instead of downgrading, I'm aware that not everyone makes regular backups of their profile (you should!) and I'm fairly certain there currently isn't any issue with downgrading to 28.17 and then back up to 29.2.

Thank you very much, it went well.

As per Murphy's law, this occured on the only machine I have yet to set up automated backups for appdata files (low on a big to-do list as data loss on it was deemed highly inconvenient but not critical) AND this was the one time I skipped on reading the release notes as I have upgraded from 28.x to 29.0.0 on multiple other machines without issues. I have probably forgot about the 28.17.0 requirement since they were already on it so it hadn't stuck.

Downgrading won't help without profile mangling cause the NEW nss store version 9 files will have been generated already preventing a migration of nss store version 8 files. One would have to remove the version 9 files THEN run the touchbase application version so that the store migration proceeds. Of course, profile mangling excludes one from implicit support and anything else is at our sufferance since they should be performing proper backups anyway. Given that the Profile Migration authoritative document exists as well as even before the recent revision to our Release Engineering Cycle.. our releases have been fairly predictable.

Granted, I have skipped the release note check on this one in this case and any data loss would be on the end user for not backing up, but the reality is >95% of users never read release notes, even more so for browser updates. A version number jump check warning during the upgrade would be appreciated when breaking changes of this magnitude are made.

[New Tobin Paradigm]

There is no effective way for an older version to know a newer version is going to do something. Regardless, release notes and other ancillary documentation are out there and there are consequences for not bothering to read it when every effort is made to publish them. We are not responsible for those consequences.

In fact, we aren't responsible for any consequences regarding the use or fitness of Pale Moon. Says so right in the MPL.

6. Disclaimer of Warranty
Covered Software is provided under this License on an “as is” basis, without warranty of any kind, either expressed, implied, or statutory, including, without limitation, warranties that the Covered Software is free of defects, merchantable, fit for a particular purpose or non-infringing. The entire risk as to the quality and performance of the Covered Software is with You. Should any Covered Software prove defective in any respect, You (not any Contributor) assume the cost of any necessary servicing, repair, or correction. This disclaimer of warranty constitutes an essential part of this License. No use of any Covered Software is authorized under this License except under this disclaimer.