FWIW, sudo aptitude pinentry-ncurses;sudo aptitude purge pinentry-gtk2
or simply sudo update-alternatives --config pinentry should fix the
issue for those with headless installations.
Maybe having gpg-agent depend on pinentry-ncurses | pinentry-gtk2 |
pinentry would be a better option over the
make that
sudo aptitude install pinentry-ncurses;sudo aptitude purge pinentry-
gtk2 or simply sudo aptitude install pinentry-ncurses;sudo update-
alternatives --config pinentry
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
@Michael: What about invoking gnupg by kmail with the related switch
instead of relying on having this option in the user configuration? This
sounds more reasonable to me and it won't break any behaviour.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
I don't believe that would work as the Xsession.d file for gnupg-agent
starts the gnupg-agent only if use-agent is active in the
configuration file.
As I don't use KDE and kmail, I don't know if use-agent is the only
solution to let kmail work with gnupg. Better talk to some kubuntu devs
about
It was added to enable gnupg support in kmail (see bug 15485).
--
gpg uses popup dialog instead of cli by default
https://bugs.launchpad.net/bugs/367163
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
I think the use-agent option should not be enabled by default.
As mentioned above: It breaks lots of scripts, and makes no sense to
have a command line app also use a gui dialog by default, when it can do
the same thing in cli just fine.
I've also looked around for an explanation for this
That is IMO a self-caused issue in Ubuntu. In the Ubuntu package the
`use-agent' option is enabled by default (#15485). Turn it off and be
satisfied.
I'm closing this, as Ubuntu has explicitly enabled this option be
default. Please reopen your report if you wish to revert this change
(JFTR: I'm
