I can confirm this is still occurring in Maverick as of this morning. The kernel fix doesn't appear to be catching all instances of the problem.
I can confirm this is still occurring in Maverick as of this morning. The kernel fix doesn't appear to be catching all instances of the problem.