Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 19 Oct 2021 17:33:14 +0000
From:      bugzilla-noreply@freebsd.org
To:        ports-bugs@FreeBSD.org
Subject:   [Bug 259281] problems after upgrade to gnupg 2.3.3
Message-ID:  <bug-259281-7788@https.bugs.freebsd.org/bugzilla/>

next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D259281

            Bug ID: 259281
           Summary: problems after upgrade to gnupg 2.3.3
           Product: Ports & Packages
           Version: Latest
          Hardware: Any
                OS: Any
            Status: New
          Severity: Affects Only Me
          Priority: ---
         Component: Individual Port(s)
          Assignee: ports-bugs@FreeBSD.org
          Reporter: b@nln.ai

After upgrade to gnupg 2.3.3 on multiple systems I started to experience is=
sues
of connecting to gpg-agent. While gpg-agent is running, when I attempt to s=
end=20


    gpg-connect-agent KILLAGENT /bye


I run into issue where one of the processes get stuck.

In addition to this, when running any gnupg command, I see error message=20

   gpg: error reading symlink '/proc/curproc/file': No such file or directo=
ry


I understand that there is not a lot of information, but I don't see a way =
to
troubleshoot this further.

Fixed this by reverting to 2.3.2


    sudo pkg install /var/cache/pkg/gnupg-2.3.2.pkg

--=20
You are receiving this mail because:
You are the assignee for the bug.=



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-259281-7788>