Has this problem resurfaced now with OS X V10.6.8? It has for me - where's the fix?
The knowledge base articel http://support.apple.com/kb/TS2998 simply says upgrade to 10.6.1 - so there was a bug! Now it seems to have started again with v10.6.8
Help!!!!
Mac OS X (10.6.8)
