Comment 14 for bug 254223

I can confirm that this bug is very much alive on a fresh install of Ubuntu 9.10 Karmic Koala, amd64. And it's now well over one year since it's been reported ... I guess you guys just don't give a damn? That's the only explanation I have for absolutely nobody from Ubuntu giving up 30 seconds of their precious time to type "We're looking into it".

Anyone know of some super-secret channel that can be used to actually get the attention of Ubuntu packagers? I'm all ears.