Your testing here is not indicative of a problem; these are expected outputs for these inputs. Sending input directly into gpg without any arguments is to decrypt or validate signed content. You would need to use command line arguments to tell gpg to encrypt or sign or ascii-armor your input.
However, if you're finding that gpg doesn't work via programs that used to work, check your ~/.gnupg/pubring.gpg file -- it may be zero bytes. See if you have a backup in ~/.gnupg/pubring.gpg~ that you can use instead. I understand gpg does not handle being interrupted very well. Thanks -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1308335 Title: gnupg never asks for passphrase – bails out with "bad passphrase" immediately To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnupg/+bug/1308335/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
