Description of problem: open gpa and goes right to an error message over a 'you dont not have a private key yet' window. window:'gpa error" 'the gpgme library returned an unexpected error.' 'the error was: invalid crypto engine.' 'this is probably a bug in gpa.' 'gpa will now try to recover from this error.' new window: 'GnuPG is rebuilding the trust database.' 'This might take a few seconds.' then seems to lock up but might still be working on list? it didnt actually crash and dont see any gpg/gpa lines in message log but at same time didnt seem happy. eventually managed to closed it after a few minutes of it not repsonding to clicking and with no obvious processor or harddrive activity. for what its worth i think that this the second time i started gpa (still havent generated keys) and i didnt generate keys during the first time i started it so maybe that confused it. Version-Release number of selected component (if applicable): gpa-0.9.0-1.fc14 (x86_64) How reproducible: dont think happened first time opened but the next few it seems to reoccur Steps to Reproduce: 1. open gpa 2. get error messages right away 3. wait to see if it does something or crashes 4. after a few minutes (and sometimes right away) it will let me cancel out fothe error message popups and let me close program window. Actual results: get error message popups Expected results: no error message popups but should let me begin to generate key Additional info:
*** Bug 663578 has been marked as a duplicate of this bug. ***
Same problem on i686 platform. GPA is now unusable.
I receive "The GPGME library returned an unexpected error. The error was: invalid crypto engine. This is probably a bug in GPA. GPA will now try and recover from this error." It never recovers and GPA is unusable gnupg 1.4.11-2.fc14 Predictably re-creatable each time the program is invoked. I currently have a private and public key.
still seeing this. Any progress on fixing the bug? Harish
I'm also seeing this problem. I had no problems with the previous version (0.8.0-3.fc13.x86_64).
I confirm this bug on a fedora 14 64bit install.
*** Bug 680845 has been marked as a duplicate of this bug. ***
Any news on the issue? I am experiencing the same problem as Done Fore, I am running Fedora 14 x86_64 QatQat
the status seems to be that gpa isnt in f15/f16 repos so continue use seahorse as workaround for now?
This message is a notice that Fedora 14 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 14. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At this time, all open bugs with a Fedora 'version' of '14' have been closed as WONTFIX. (Please note: Our normal process is to give advanced warning of this occurring, but we forgot to do that. A thousand apologies.) Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, feel free to reopen this bug and simply change the 'version' to a later Fedora version. Bug Reporter: Thank you for reporting this issue and we are sorry that we were unable to fix it before Fedora 14 reached end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged to click on "Clone This Bug" (top right of this page) and open it against that version of Fedora. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping