Sigh. This keeps happening: I report a bug, then sometime after I've upgraded away from the Ubuntu version I found the problem in, the bug gets triaged with the message that it would be helpful if I could reproduce the problem with a mainline build because then more people could look at it. And it gets marked as Incomplete. And then before I get around to doing that, or sometimes when I do, the bug is marked as Expired.
The canned message clearly implies that the problem can still be looked at if the user doesn't test with a mainline kernel (as you would expect from a normal user whom we don't expect to understand the gobbledygook about looking up their current kernel version in a kernel mapping and installing the current mainline *image*.deb for their version and architecture). But marking the bug as Incomplete means that you intend for the bug to be ignored in its present state. Can you at least update your message to say "we're not going to look at your problem until you do this"? And the user probably also needs to move the bug's status to New after testing with a mainline kernel (assuming Launchpad will allow that) because otherwise the bug is going to expire regardless. By the way, about this particular suspend problem: I've seen it with Natty as well, but it's harder to reproduce because suspend seems to be broken right now. On a further note, the page about mainline kernels links to a "current" build that doesn't actually have any kernel packages, only the kernel headers for amd64 and "all." -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/704962 Title: Can't connect to bluetooth headset after suspend -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
