Bug #21182 [Com]: Uncaught Crypt_GPG_Exception: Unknown error getting GnuPG version information

Edit report at https://pear.php.net/bugs/bug.php?id=21182&edit=1 ID: 21182 Comment by: kyra@existing.me Reported By: kyra at existing dot me Summary: Uncaught Crypt_GPG_Exception: Unknown error getting GnuPG version information Status: Open Type: Bug Package: Crypt_GPG Operating System: Linux (Xubuntu) Package Version: 1.6.0b3 PHP Version: Irrelevant Roadmap Versions: New Comment: @alec Is there any additional info I should provide to get this worked on and fixed? =o) Previous Comments: ------------------------------------------------------------------------ [2017-02-14 08:46:00] kyrad -Status: Bogus +Status: Open re-opening as the bug you referenced has since been deleted and this is thus no longer a dupe. ------------------------------------------------------------------------ [2017-02-13 08:22:31] kyrad It says "The user who submitted this bug has not yet confirmed their email address." I was having issues with submitting the form and getting a confirmation email. I know I accidentally opened 21181 and I closed it as a dupe when I found out. If I had erroneously submitted additional ones please invalidate them. From my understanding 21180 will expire in 24hrs anyways, thus making this bug the primary one. I apologize for the confusion. ------------------------------------------------------------------------ [2017-02-13 02:37:40] alec #21180. ------------------------------------------------------------------------ [2017-02-12 14:25:52] kyrad > Because of this, we hope you add your comments to the existing bug instead. It would be nice to be told what bug # it is. There are only 2 open bugs listed here: https://pear.php.net/bugs/search.php?cmd=display&package_name[]=Crypt_GPG&status=Open Neither of them describe what I am experiencing. =o\ ------------------------------------------------------------------------ [2017-02-12 07:56:59] alec -Status: Open +Status: Bogus Please do not submit the same bug more than once. An existing bug report already describes this very problem. Even if you feel that your issue is somewhat different, the resolution is likely to be the same. Because of this, we hope you add your comments to the existing bug instead. Thank you for your interest in PEAR. Duplicate. ------------------------------------------------------------------------ The remainder of the comments for this report are too long. To view the rest of the comments, please view the bug report online at http://pear.php.net/bugs/bug.php?id=21182 -- Edit this bug report at https://pear.php.net/bugs/bug.php?id=21182&edit=1