It was likely the kernel scheduler. I did not say this because I did not trust my judgment. So your rule is to ignore bugs without a package assigned? And you don't even ask? Bad rule.
On 08/29/2010 12:35 AM, Fabio Marconi wrote: > Hello kornelix > I admit that is not easy to understand, but if there was un update that > solves a bug, here in Launchpad we cannot know the root cause, only > developers know that. > Is not the bug that is invalid, but the report, actually solved. > Launchpad is the media to transmit a bug to the right developer (or team), we > are a small group (bugsquad) that contact the reporter, if possible try to > reproduce the bug, analize the attached informations and if everythings is ok > confirm the report, then the report came to the triagers, then to the > developer/s. > Due to the complexity of the OS everyone of us have assigned a package. > Why your valid report still waiting so long? > Because you don't have assigned it to a package (affects: ubuntu → linux > (Ubuntu) ) in the yellow stripe. > So if you want a valid response from the mechanism, please take a look here: > https://wiki.ubuntu.com/Bugs/FindRightPackage or remember to assign the > package. > Fabio > -- erratic thread scheduling, kernel 2.6.31 https://bugs.launchpad.net/bugs/459628 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
