It appears that the firefox setting to clear "saved passwords" (introduced in 25/1/2011 release), does more than might be expected.
It deletes key3.db, which is generated by firefox to encrypt session data (including stored passwords and certificates). This also affects addons such as session manager. This means ticking to clear "saved passwords" will result in being unable to decrypt saved sessions, losing all session information (including open windows / tabs etc.). This is not obvious when you tick "saved passwords".
It also results in the loss of other personal certificates, which may be used to access some web sites.
This needs to be documented. If you really want to delete certificates, even when password protected by the user, perhaps it might best be done by splitting it out into a more obvious separate option.
I've already spent time recovering from, investigating and reporting this bug. You've given no response other than "we'll look into it", and now - "test it yourself".
Why can't you say yes/no to "is the bug fixed in the latest version" ? Are you seriously suggesting I spend more time re-testing the new version of your software, without first even knowing this ?
Your saying "Your software", " You've given no response" and "Why can't you say yes/no to "is the bug fixed in the latest version"
First of all neither Alan,Myself or anyone else who will give answers other than "Thanks we'll look into this" or "please provide x information" work for Piriform; we are all just members like you. The Fact that you got a reply from Mr T "Thanks we'll look into this" means that your bug is currently being looked at by the development team.
This is the ONLY information they EVER give to anyone until the fix is in. You'll know the fix is in because the development staff will 1)state so in this thread and/or place a note in the change log about the specific request. Rarely in any software is a fix for an issue so easy to fix that less than 30 days after a bug fix is reported.
This is especially true in a request like yours. The Development time (I would assume) is looking into ways of removing saved passwords yet keep the db file you mention.
For a quick fix on your end do one or both of these actions:
Add key3.db to your exclude list
uncheck Saved Passwords under Firefox.
Finally I assure you: if a developer has made even a slight mention in your thread it means they are finding a fix. Often they will not even reply they will just look into it. Please learn some patience and remember that this software is provided to you free of charge.
I referred to a comment I noticed in the new release (3.05.1408) which says "Improved Firefox/Mozilla Saved Password cleaning." ? This could refer to the issue I reported, which is why I asked. My question was addressed to Piriform. I patiently await their reply.
I have already unchecked Saved Passwords under Firefox.