I have this problem testing Cosmic as well. In fact it is a problem both when using a virtual tty (alt-cntl-F2 for example), and when using ssh.
The problem appears to me to be that pinentry, the program to collect the passphrase for one's private key, is not working as it was. Assuming I am not signed on elsewhere, first entering the following works for me: GPG_TTY=$(tty) export GPG_TTY Ideally this would go in your shell startup script, e.g. .bashrc. It's from "man gpg-agent". But it gets stranger and then the above is not enough. If I am signed on a graphic session, when I try to use my private key through either an ssh session or a virtual terminal, the prompt for unlocking the private key goes to the graphic session rather than to where I'm typing. That happens even if the graphic session is locked and invisible. In this case the gpg "--pinentry-mode loopback" option works to have a passphrase prompt go to where I'm typing (though the prompt is very basic compared to the text pop-up). Should user set-up add the above GPG_TTY commands to everyone's .bashrc for the first case? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1775923 Title: gpg can't access secret keys when logged in via ssh instead of desktop To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnupg2/+bug/1775923/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
