This problem has been reported and blogged about over a month. Still a problem.
How many "engineers" are working on this?
Or is it just added to the backlog of software fixes, and will be handled eventually?
Since some update caused this problem in March or April, how hard can it be to fix?
