Timeout error

Asked by luboss

I tried several times to file a bug but I'm still getting the same message:

Timeout error
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.
Trying again in a couple of minutes might work.
(Error ID: OOPS-1683L564)

I don't understand why does it happen. Maybe something with network. It's very annoying, I've found real issue which I have to deal with but cannot even file a bug.

Question information

Language:
English Edit question
Status:
Solved
For:
Launchpad itself Edit question
Assignee:
No assignee Edit question
Last query:
Last reply:
Revision history for this message
Curtis Hovey (sinzui) said :
#1

This is a bug that the Launchpad bug team is actively working on. This is a case where Launchpad is doing too much work to file a bug.

Revision history for this message
luboss (lubos-katrinec) said :
#2

Ok, but how can I file a bug then? I'm stucked :-(

L.

On 10 August 2010 18:14, Curtis Hovey
<email address hidden>wrote:

> Your question #120596 on Launchpad Bugs changed:
> https://answers.edge.launchpad.net/malone/+question/120596
>
> Status: Open => Answered
>
> Curtis Hovey proposed the following answer:
> This is a bug that the Launchpad bug team is actively working on. This
> is a case where Launchpad is doing too much work to file a bug.
>
> --
> If this answers your question, please go to the following page to let us
> know that it is solved:
>
> https://answers.edge.launchpad.net/malone/+question/120596/+confirm?answer_id=0
>
> If you still need help, you can reply to this email or go to the
> following page to enter your feedback:
> https://answers.edge.launchpad.net/malone/+question/120596
>
> You received this question notification because you are a direct
> subscriber of the question.
>

Revision history for this message
Deryck Hodge (deryck) said :
#3

We're doing a rollout of new code tomorrow, which should fix the problem. Until then, you can try our edge server, which should allow you to file the bug.

https://bugs.edge.launchpad.net/ubuntu/+filebug

Please note, though, that filing a bug this way is not recommended. You should be using apport or filing the bug on the package in Ubuntu, not against Ubuntu itself without specifying the package. See https://help.ubuntu.com/community/ReportingBugs for more about reporting bugs in Ubuntu.

Cheers,
deryck

Revision history for this message
luboss (lubos-katrinec) said :
#4

ubuntu-bug is not an option for me because the package which is the bug
about doesn't exist at all. (it seems it disappeared from repositories).

But the link:
http://bugs.launchpad.net/ubuntu/+source/PACKAGENAME/+filebug?no-redirect

from the "ReportingBugs" page works and I finally submitted a bug.

Thanks & regards,

Lubos

On 11 August 2010 13:36, Deryck Hodge
<email address hidden>wrote:

> Your question #120596 on Launchpad Bugs changed:
> https://answers.edge.launchpad.net/malone/+question/120596
>
> Status: Open => Answered
>
> Deryck Hodge proposed the following answer:
> We're doing a rollout of new code tomorrow, which should fix the
> problem. Until then, you can try our edge server, which should allow
> you to file the bug.
>
> https://bugs.edge.launchpad.net/ubuntu/+filebug
>
> Please note, though, that filing a bug this way is not recommended. You
> should be using apport or filing the bug on the package in Ubuntu, not
> against Ubuntu itself without specifying the package. See
> https://help.ubuntu.com/community/ReportingBugs for more about reporting
> bugs in Ubuntu.
>
> Cheers,
> deryck
>
> --
> If this answers your question, please go to the following page to let us
> know that it is solved:
>
> https://answers.edge.launchpad.net/malone/+question/120596/+confirm?answer_id=2
>
> If you still need help, you can reply to this email or go to the
> following page to enter your feedback:
> https://answers.edge.launchpad.net/malone/+question/120596
>
> You received this question notification because you are a direct
> subscriber of the question.
>

Revision history for this message
Deryck Hodge (deryck) said :
#5

Closing as solved.