Comment 13 for bug 177076

Hi Guys,

I'm glad to hear there is at least a workaround for this bug. I spoke with a member of the kernel team and this is probably as good as this will get in terms of a "solution" prior to the Hardy Heron release. It is not a matter of importance of the bug, but rather the amount of resources we have available to resolve it. With the development cycle for Hardy now entering feature freeze, the teams must now focus on resolving high and critical bugs which have no fixes or documented workarounds. I'll leave this report open, but this will be marked as "Won't Fix" for the Hardy release. Thanks.