Launchpad itself

Pygpgme can raise Invalid crypto engine importing new key

Bug #209902 reported by Diogo Matsubara
10
Affects Status Importance Assigned to Milestone
Launchpad itself
Fix Released
Critical
Unassigned

Bug Description

OOPS-820EC26 and OOPS-820EC27 show that a GpgmeError: (7, 150, 'Invalid crypto engine') can be raised importing a new gpg key.

That exception should be caught and a nice error message shown to the user. It seems that the user who triggered this error sucessfully registered the key, which implies that trying again might just work.

Another occurance: OOPS-823EB73

See original description
Revision history for this message
Diogo Matsubara (matsubara) wrote :

One thing I noticed is that both users that triggered the error (the OOPS in this report and in the duplicate) appear to be using a 64bit cpu.

Changed in launchpad:
status: New → Confirmed
Revision history for this message
Diogo Matsubara (matsubara) wrote :

I've chatted with jamesh about this. He asked me to check if the gpg versions of the app server were upgraded.

Checked with mthaddon, and doesn't seem related to version differences. We had one OOPS on a dapper server and another on a edgy server. https://pastebin.canonical.com/3787/ has the versions running on each server.

description: updated
Diogo Matsubara (matsubara)
Changed in launchpad-foundations:
status: Confirmed → Triaged
importance: Undecided → Low
Robert Collins (lifeless)
Changed in launchpad:
importance: Low → Critical
Revision history for this message
Curtis Hovey (sinzui) wrote :

This oops has not been seen since 2008.

Changed in launchpad:
status: Triaged → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Subscribing...

Other bug subscribers

Remote bug watches

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