Ted Unangst wrote: > I'm not sure where the bug is exactly (seems probable it could be an apple > problem), but for the record...
I think this was fixed with an apple update? Nothing in the release notes of course, but it doesn't seem to happen anymore.
