[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Fwd: error 500 when clicking bug link



On Sat, 2 Feb 2019, David Wright wrote:

> Date: Sat, 2 Feb 2019 10:44:23
> From: David Wright <deblis@lionunicorn.co.uk>
> Reply-To: debian-user@lists.debian.org
> To: debian-user@lists.debian.org
> Subject: Re: Fwd: error 500 when clicking bug link
> Resent-Date: Sat,  2 Feb 2019 15:44:42 +0000 (UTC)
> Resent-From: debian-user@lists.debian.org
>
> On Sat 02 Feb 2019 at 12:21:00 (+0100), Andrea Borgia wrote:
> > I reported this issue a couple of weeks ago and I haven't heard back
> > from anyone. The problem is still there: how do I bring this to the
> > attention of someone who can actually fix it?
> >
> > -------- Messaggio Inoltrato --------
> > To: owner@bugs.debian.org
> > From: Andrea Borgia <andrea@borgia.bo.it>
> > Subject: error 500 when clicking bug link
> > Date: Sun, 20 Jan 2019 18:38:47 +0100
> > From this report https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=919227
> >
> > I clicked the link next to "Package:" at the top:
> > https://bugs.debian.org/cgi-bin/pkgreport.cgi?src=linux
> >
> > and I get repeated errors:
> > "500 internal server error"
> >
> > I'm reporting as recommended by the message.
>
> Maybe it's been fixed. When I click on that link, I arrive at
> https://bugs.debian.org/cgi-bin/pkgreport.cgi?src=linux
> which looks like:
>
> Debian Bug report logs: Bugs in source package linux
>
> Maintainers for linux are Debian Kernel Team <debian-kernel@lists.debian.org>.
>
> You may want to refer to the following individual bug pages: hyperv-daemons, libbpf-dev, libbpf4.19, libbpf4.20,
>
> This list goes on for ages, then after that it looks like a normal
> bugs page. Just the saved text on the page is:
> $ wc /tmp/wbp
>   2505  32837 283641 /tmp/wbp
>
> Cheers,
> David.
>
Has the O.P. logged into the website before trying to click that link?
Usually errors in the 500 range happen because access is forbidden and
that can happen if you're not already logged into an account with enough
access privileges on it.

>

--


Reply to: