gnupg-agent: no longer writes $GNUPGHOME/gpg-agent-info-$(hostname) file

Bug #1566928 reported by Dimitri John Ledkov on 2016-04-06
This bug affects 1 person
Affects Status Importance Assigned to Milestone
gnupg2 (Debian)
gnupg2 (Ubuntu)
Dimitri John Ledkov
Dimitri John Ledkov

Bug Description

Imported from Debian bug


Dimitri John Ledkov (xnox) wrote :

we need fixes to our user-space upstart jobs to export the standard agent info location

Changed in gnupg2 (Ubuntu):
status: New → Triaged
importance: Undecided → Critical
Changed in gnupg2 (Ubuntu Xenial):
assignee: nobody → Dimitri John Ledkov (xnox)
Changed in gnupg2 (Debian):
importance: Undecided → Unknown
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package gnupg2 - 2.1.11-6ubuntu2

gnupg2 (2.1.11-6ubuntu2) xenial; urgency=medium

  * Fix upstart user-session integration with new pinentry:
  - restart gpg-agent, once dbus is started, such that agent has DBUS
    session environemnt set and can connect to the pinentry-gnome3 Closes:
    #790316 Closes: #795368 LP: #1566928
  - use gpgconf to launch/kill gpg-agent and to check settings

 -- Dimitri John Ledkov <email address hidden> Fri, 08 Apr 2016 08:55:10 +0100

Changed in gnupg2 (Ubuntu Xenial):
status: Triaged → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.