+++ This bug was initially created as a clone of Bug #548136 +++

Please describe the problem:
If the password contains "%" followed by any *two* characters, i.e. "%sf" or "%vd", you will not be able to use seahorse to decrypt a private PGP key that was originally encrypted with gpg.  This means that you cannot change the key's password using seahorse nor can you use seahorse-agent to fetch your private key for signing text, etc.  If the private key is created or otherwise encrypted with seahorse using one of these passwords, gpg will not be able to decrypt the private key.

Steps to reproduce:
1. Create a new public/private key pair using gpg as follows:
   GPG_AGENT_INFO="" gpg --gen-key
2. Accept defaults for key type and key size, enter some user name, etc.
3. For the password enter "%ss".
4. Start seahorse and attempt to change the password for the new key.


Actual results:
No matter what password you enter, you will always receive an invalid password response.

Expected results:
Entering "%ss" as the password should allow you to go about changing the password on the new key.

Does this happen every time?
Yes.

Other information:
It's possible to turn around the presented scenario and create a public/private keypair using seahorse and a password as specified.  gpg will be unable to decrypt the key using that password even though seahorse will be able to do so.   It's also possible to use seahorse to change the password on an existing key (as long as the password does not have the bad form) to a password which gpg will not be able to use to decrypt the key.

Basically, it looks like the password dialogs for seahorse are malfunctioning.