Launchpad itself

Unable to reactivate PGP key

Bug #775885 reported by Bryan Donlan
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Launchpad itself
Invalid
Critical
Unassigned

Bug Description

When I try to reactivate my PGP key 4096R/E0883D1C, I get the following error:

Oops!
Sorry, something just went wrong in Launchpad.

We’ve recorded what happened, and we’ll fix it as soon as possible. Apologies for the inconvenience.

(Error ID: OOPS-1948DQ476)

Entering in the full fingerprint simply tells me the key is already registered and can be reactivated, but does not actually reactivate it.

Note that this key expired recently, and I just uploaded a new copy with a new expiration date to the ubuntu keyserver - could this be relevant?

Tags: gpg oops
Revision history for this message
Bryan Donlan (bdonlan) wrote :

Update: The reactivation just now succeeded, but the fact that there's a bug remains :)

Robert Collins (lifeless)
Changed in launchpad:
status: New → Triaged
importance: Undecided → Critical
tags: added: oops
Revision history for this message
William Grant (wgrant) wrote :

  Module canonical.launchpad.database.logintoken, line 157, in sendGPGValidationRequest
    key.fingerprint)
  Module canonical.launchpad.utilities.gpghandler, line 358, in encryptContent
    ctx.encrypt([key], gpgme.ENCRYPT_ALWAYS_TRUST, plain, cipher)
GpgmeError: (0, 1, u'General error')

It probably still had the expired key.

William Grant (wgrant)
tags: added: gpg
Revision history for this message
William Grant (wgrant) wrote :

Expired keys are handled fine, and I can't reproduce this OOPS any other way. Hopefully we'll find another occurrence in the OOPS report eventually.

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

Other bug subscribers

Remote bug watches

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