Created attachment 1051514 [details] signonly.pub Version-Release number of selected component (if applicable): gnupg2-2.1.5-1.fc22.x86_64 Steps to Reproduce: 1. mkdir y 2. GNUPGHOME=$(pwd)/y gpg2 --import - < tests/keys/signonly.pub 3. GNUPGHOME=$(pwd)/y gpg2 --import - < tests/keys/signonly.sec 4. echo Hello > in 5. GNUPGHOME=$(pwd)/y gpg2 --encrypt --always-trust -r 15E7CE9BF1771A4ABC550B31F540A569CB935A42 --output out -- in Actual results: gpg2 consumes 100% CPU, per bug 1239813 apparently indefinitely Expected results: Something like what happens with s/gpg2/gpg/g: > gpg: 15E7CE9BF1771A4ABC550B31F540A569CB935A42: skipped: unusable public key > gpg: in: encryption failed: unusable public key Additional info: This breaks pygpgme test suite / build.
Created attachment 1051515 [details] signonly.sec
gnupg2-2.1.7-1.fc23 has been submitted as an update for Fedora 23. https://admin.fedoraproject.org/updates/gnupg2-2.1.7-1.fc23
gnupg2-2.1.7-1.fc22 has been submitted as an update for Fedora 22. https://admin.fedoraproject.org/updates/gnupg2-2.1.7-1.fc22
Package gnupg2-2.1.7-1.fc22: * should fix your issue, * was pushed to the Fedora 22 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing gnupg2-2.1.7-1.fc22' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2015-13444/gnupg2-2.1.7-1.fc22 then log in and leave karma (feedback).
FWIW, confirmed 2.1.7-1.fc24 fixes it. Thanks!
gnupg2-2.1.7-1.fc22 has been pushed to the Fedora 22 stable repository. If problems still persist, please make note of it in this bug report.
gnupg2-2.1.7-1.fc23 has been pushed to the Fedora 23 stable repository. If problems still persist, please make note of it in this bug report.