P: CS4, CS5, CS6, CC: Cursor disappears on Mountain Lion (MacOS 10.8)

hmm, as I have said, I did not have this problem until Lion was installed. -its a early2008-20-4GB. While I do not have a normal computer workload right now, I have been testing as much as possible- RTMO. I have not seen the problem...yet? I have an over-due list of waiting C's at the board, I cant give the screen the usual 10 right now. My sympathy as well Ray. Is photoshop no more?

That is a drag of a job Ray, sympathy for that result.

If you're going to try a clean re-install, although this isn't likely to fix the issue as it's looking more and more likely a low-level OS cursor module not handling a non-standard screen drawing request properly (as, ahem, originally stated by Chris), it's a good plan to do it by creating a new partition (if you have the space) or using another disc (if you have one) and installing onto that as a test volume. That way you can continue working (slowly I know because of the shy cursor) and test when you've got a minute.

Apple changed a lot of the underpinnings of OSX when they upgraded Lion to ML, not least of which is the handling of display profiles by ColorSync, something else which remains unfixed.

The only way to get this sorted is to bump it up Apple's bug list. That might have been easier ten years ago before the iThings appeared, but I fear we are a very small voice now.

Sorry, I did a complete clean re-install. A big big PITA having to de-activate dozens of applications and re-installing them.

Unfortunately after this the problem is still there.

I have complained several times with Apple but this seems to be to no avail. I guess the number of affected users for Adobe might be noticeable but amongst all Apple users I think we aren't even a blip on the radar.

I really really hope Adobe has escalated this all the way by now.

TH, EUREKA! Thanks for sharing your experience. And may the Force continue to be with you!

Chris Cox, it looks like you (and Adobe) may be off the hook. Thanks for your patience.

So a clean OS install behaves different from an upgrade OS install - interesting.

The total re-install has worked. I no longer have the problem with photoshop and everything else works the same way it did- fine. I am not a tech, nor a engineer. I am the customer. Over a week of my valuable time to fix something I should not have to. Caution to all who install Lion on top of another OS and expect Adobe to have worked out their issues....

Judy is completely correct; bugs are triaged and fixed (by ALL software companies) based on the importance to the customer and the feasibility of the fix. Often the number of complaints is in some way a surrogate for customer importance...and clearly, there have been LOADS of complaints to Adobe about this bug, so if a solution were possible, the priority would be VERY high...

In this case, there is ZERO feasibility of an Adobe fix as we have no control over the offending code. The best course of action to make sure the problem is reported clearly to those in the position to make a change. Multiple voices raise the awareness of the issue as something that's important to the user community. In this regard, yes, customers have more clout than other software firms.

In other words, yes, lots of complaints to those able to perform the required engineering (in this case, Apple) makes it WAY more likely that a bug (anyone's bug) will get prompt and complete attention.

Mountain Lion is buggy, only Apple can fix, and will fix if it hears from enough customers.We all need to post on the Apple forums, not just Adobe. I was in an Apple store, and the manager said I should call applecare and ask to have the problem elevated to developers. The more complaints they get, the higher priority they give it. Post and call guys!!

No, I can't be much more specific due to NDAs with Apple. (I'm probably stretching the rules a bit much already)

I do not think the Apple support people are lying. At least the ones I've spoken to didn't seem to be. Perhaps they just are not trained as throughly as you Chris.
I'm still not understanding that if you know so much about this issue that you can't share the info with us professionals here, so we can start to get this problem resolved.