[15:06] <sur5r> hi everyone. can anyone tell me how to proceed when i consistently get oopses when trying to log in to launchpad? ubuntuone login itself is working...
[15:57] <cjwatson> sur5r: Can you give us the OOPS ID?
[16:03] <cjwatson> sur5r: (we can fix it for you if you do)
[16:04] <sur5r> let me generate a new one *g*
[16:05] <sur5r>  OOPS-276c9cbd23332010a7cfaefde7ab8da2
[16:06] <sur5r> cjwatson: there you go
[16:07] <cjwatson> thanks.  oh for goodness's sake, oops.c.c is lagging again.  this may take a while - how about I email you when it's done?
[16:08] <sur5r> no hurry
[16:08] <sur5r> i fighting this for months now
[16:08] <sur5r> *i'm
[16:09] <cjwatson> OK, we should really fix this damn bug - https://bugs.launchpad.net/launchpad/+bug/1607242
[16:09] <cjwatson> which is almost certainly what you're running into
[16:09] <sur5r> i suspected sth. like that
[16:09] <sur5r> because my mail address is known to launchpad because of debian packages i maintain
[16:09] <cjwatson> right, a typical case
[16:09] <cjwatson> anyway, we have a strategy to fix it, I'll do it once the oops analysis system catches up
[16:10] <sur5r> thanks a lot
[16:11] <sur5r> btw.: login-support@c.c seems to be aliased to /dev/null
[16:12] <sur5r> or isd-support@ whatever
[16:13] <cjwatson> I don't know about that part of it I'm afraid
[16:13] <sur5r> i thought as much
[16:14] <sur5r> it's just that those addresses are where you end up when trying to use mail to solve the problem
[16:14] <sur5r> should've come here right away *g*
[16:15] <cjwatson> trying to find out where it currently goes
[16:23] <cjwatson> apparently it goes to an RT queue that I've been meaning to get access to for ages and have never got round to it, so I'll chase that up
[16:28] <sur5r> *G*