Indeed, after posting this I discovered that I had to turn it on
manually and edit my startup properties. Should this be automated, so
Evolution gpg works?
--
seahorse
https://launchpad.net/bugs/58274
--
ubuntu-backports mailing list
ubuntu-backports@lists.ubuntu.com
https://lists.ubuntu.com/m
After this upgrade, the GNUPG integration in Evolution stopped working.
See attachment for the error message.
--
seahorse
https://launchpad.net/bugs/58274
--
ubuntu-backports mailing list
ubuntu-backports@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-backports
Well, not everyone wants the GPG agent to be running all the time. What it
eventually boils down to is a GPG bug that I first discovered when testing
bzr's gpg signing capability. Basically, if it cannot connect to the GPG
agent, it always returns a failure code. I filed the bug upstream and the
ne
is your seahorse-daemon running? it changed names from seahorse-agent to
seahorse-daemon.
--
seahorse
https://launchpad.net/bugs/58274
--
ubuntu-backports mailing list
ubuntu-backports@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-backports
* Trying to backport seahorse...
-
-
-
I: Extracting seahorse_0.9.3-0ubuntu5.dsc ... done.
I: Building backport of seahorse-0.9.3 ... done.
** Changed in: dapper-backports (upstream)
Assignee: (unassigned) => Colin Watson
Status: In Progress => Fix Released
--
seahorse
ht
Approved for backporting
** Changed in: dapper-backports (upstream)
Importance: Untriaged => Wishlist
Status: Unconfirmed => In Progress
Target: None => stable
--
seahorse
https://launchpad.net/bugs/58274
--
ubuntu-backports mailing list
ubuntu-backports@lists.ubuntu.com
https
