Cannot import gpg key - Timeout

Bug #1753019 reported by backports242 on 2018-03-02
42
This bug affects 5 people
Affects Status Importance Assigned to Milestone
Launchpad itself
Critical
Colin Watson

Bug Description

 For both yesterday and today I have been trying to import my gpg key. Every time I try I get a timeout error with the code OOPS-5cb21cb715721f37e74f2731076de534.

Created from https://answers.launchpad.net/launchpad/+question/665140/

Peter Baumgartner (ipmb) wrote :

I'm seeing the same thing today. (Error ID: OOPS-098ac44dcdd13041bb666f5a443b8254)

backports242 (backports) wrote :

For others who end up here, there is a patch in progress which should allow the devs to debug the issue.

https://code.launchpad.net/~cjwatson/launchpad/gpg-timeline/+merge/340554

Bryan Seitz (seitz-a) wrote :

Has this been fixed yet ?

We'll close this bug when it's fixed, but I haven't got my
instrumentation branch reviewed yet so I can't make much progress until
then.

SlowStroke (slowstroke) wrote :

yes, it's working now, thanks.

​Sent from ProtonMail, encrypted email based in Switzerland.​

‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐

On March 16, 2018 1:10 PM, Bryan Seitz <email address hidden> wrote:

> ​​
>
> Has this been fixed yet ?
>
>
> ---------------------------------
>
> You received this bug notification because you are subscribed to the bug
>
> report.
>
> https://bugs.launchpad.net/bugs/1753019
>
> Title:
>
> Cannot import gpg key - Timeout
>
> Status in Launchpad itself:
>
> New
>
> Bug description:
>
> For both yesterday and today I have been trying to import my gpg key.
>
> Every time I try I get a timeout error with the code OOPS-
>
> 5cb21cb715721f37e74f2731076de534.
>
> Created from https://answers.launchpad.net/launchpad/+question/665140/
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/launchpad/+bug/1753019/+subscriptions

Colin Watson (cjwatson) wrote :

@slowstroke We haven't done anything specific to fix this, so if it worked it was probably just by good luck. I'm working on landing my instrumentation branch now.

Colin Watson (cjwatson) wrote :

OK, I now have better instrumentation (OOPS-c19ccefbed6bcb7b0d094cc14e180842) and I think I see the problem: it's essentially the same kind of thing I was working on in https://lists.gnupg.org/pipermail/gnupg-devel/2017-September/033086.html. Since a modified version of that patch has landed in gpgme 1.10.0, I'm going to backport it to our production systems.

Changed in launchpad:
assignee: nobody → Colin Watson (cjwatson)
importance: Undecided → Critical
status: New → In Progress
tags: added: lp-foundations oops timeout
Vicențiu Ciorbaru (cvicentiu) wrote :

The MariaDB Foundation is also affected by this. We are looking forward to having the timeout problem resolved. If anyone is running into this issue, I have managed to import my keys after about 20 or so tries at various intervals. So if you're really desperate I guess you can keep on trying, it might just make it through.

The verification step works without problems.

Colin Watson (cjwatson) wrote :

Our appservers are running with the backported gpgme patches now, so this should work again.

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

Duplicates of this bug

Other bug subscribers

Related questions