Further investigating I found that: $ unset GPG_AGENT_INFO
helps solving this issue. the env var in a fresh gnome terminal is set to: $ env | grep GPG_AGENT_INFO GPG_AGENT_INFO=/run/user/phaidros/keyring-xyz123/gpg:0:1 I am not very familiar with the usage of gpg agents (seahorse in the case of ubuntu?), so someone more knowledgeable might have an idea what could be wrong with that env setting, or tell me how to find out if seahorse/gpg-agent/whatever runs as expected. any hints? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1169121 Title: 13.04 Regression: cpm doesn't ask for gpg key password, but: gpgme error / bad passphrase To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cpm/+bug/1169121/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
