gnaegi wrote:
What this means is that Apple has no clue what is gonig on. Their not one step further than three weeks ago when I filed the bug initially.
It only means that engineering as yet has no fix it is ready to release to the public. Apple engineering must of necessity be certain that it understands the cause of the issue & has a reasonable certainty that any remedy for it it produces doesn't cause greater problems for users, including those that are currently having no problems.
The cause & how many users it affects plays a large part in how long this process takes. Often, an issue that affects relatively few users (& a few hundred users is very few in relation to the total user base) is harder to resolve because it may involve a revision of a particular piece of hardware included only in some model runs, the interaction of Apple & third party items (both hardware & software) that not all users use, or a combination of both.
This is why workarounds effective for some users are not for others, & why it is important to send Apple feedback (through
http://www.apple.com/feedback/) supplying every pertinent detail you can manage instead of just posting here, in the user-to-user forums.
Most of all, it is why it is a good idea to avoid the mindset that all issues with similar symptoms have similar causes, that what you read about others users' issues & what doesn't fix them means the same will be true for you, & therefore there is no point in trying on your system what they have tried on theirs.
Yours may be an issue only Apple can fix, but it may also be one only you can fix. Guessing about this is riskier than testing your system because if you guess wrong, you could wait forever for a fix that never comes.