unable to mark bug 794861 duplicate of bug 767475

Asked by Eliah Kagan

I am unable to mark bug 794861 a duplicate of bug 767475. Whenever I try, the error message described in bug 794879 (which is about the bad *way* in which the error is shown, rather than the failure itself, unless they turn out to be the same bug) occurs. The most recent time I have tried to do this, I got OOPS-1986AS45. This resembles the problem Lorenzo (https://launchpad.net/~cthol) is having trying to post a comment in bug 760814 (see https://answers.launchpad.net/launchpad/+question/160770).

Should I file a new bug report about this problem?

Revision history for this message
Eliah Kagan (degeneracypressure) said :
#1

It seems that this (and https://answers.launchpad.net/launchpad/+question/160770) may be part of a bigger problem in https://bugs.launchpad.net. I was able to post a comment in bug 791213 recently, but:

(1) When I try to mark that same bug Invalid in libqt-declarative in Arch Linux (with the message "Marking Invalid in libqt-declarative in Arch Linux, since Andrea Scarpino has deleted her comment on the upstream Qt bug tracker that had confirmed it for Arch Linux (and searching https://bugs.archlinux.org doesn't reveal a report separately confirming it)."), I get a timeout (OOPS-1986DS67).

(2) I initiated the process of submitting a bug report for a crash in gnome-power-manager in Oneiric with Apport, a while ago. I finally got around to getting back to that, and now when enter the description and click the Submit button, I get a timeout (OOPS-1986A66).

Revision history for this message
Best Gary Poster (gary) said :
#2

Bug 794802 appears to be the source of the new timeout problems.

Thank you for the heads up.

Revision history for this message
Eliah Kagan (degeneracypressure) said :
#3

Thanks Gary Poster, that solved my question.