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

  • 29
  • Problem
  • Updated 5 years ago
  • Solved
  • (Edited)
My cursor keeps disappearing with CS4 and CS5. This started after I installed Mountain Lion. I have noticed this on 2 different iMacs, one at home and one at work.
Photo of Marc Straub

Marc Straub

  • 7 Posts
  • 1 Reply Like
  • frustrated

Posted 7 years ago

  • 29
Photo of howe roger

howe roger

  • 15 Posts
  • 2 Reply Likes
This will probably be deleted but i am going back to Corel suite with paint shop pro etc included . .on PC . . . Bye bye adobe, bye bye apple I for one have grown weary of your corporate games . . . . Is a working toolkit really too much to ask after years of loyal investment? . . . . No it isn't , an investment is logically something that ultimately gives a worthwhile return I do not consider missed deadlines and lost clients a good return, not to mention the extra stress incurred.
Photo of Andrew Kinnear

Andrew Kinnear

  • 6 Posts
  • 2 Reply Likes
Bye
Photo of Ray Ketchem

Ray Ketchem

  • 36 Posts
  • 0 Reply Likes
i'm running Mountain Lion and CS6 and this problem has become a huge problem for me.

cursor disappears about every 10 minutes or so. it's terrible.
Photo of Chris Cox

Chris Cox

  • 20280 Posts
  • 848 Reply Likes
We're all still waiting on Apple to get this fixed.
Photo of Ray Ketchem

Ray Ketchem

  • 36 Posts
  • 0 Reply Likes
Really? I found quite a few comments about this from PC users too.
Photo of Chris Cox

Chris Cox

  • 20280 Posts
  • 848 Reply Likes
Given that we're discussing about a MacOS 10.8 specific video driver bug, I kind of doubt that.
Photo of Ray Ketchem

Ray Ketchem

  • 36 Posts
  • 0 Reply Likes
Duh. I don't mean within this specific thread. They pay you to work for Adobe with comments like these?
Photo of Chris Cox

Chris Cox

  • 20280 Posts
  • 848 Reply Likes
I never said within this thread...

We're talking about a single issue here that is very specific to MacOS 10.8, on AMD GPUs.

There are other driver bugs on Windows that might sound somewhat similar, but are not the same issue (by definition because they're on Windows, with different driver versions and different GPUs). Also, most of those driver bugs have been fixed, if people would just install the latest drivers.

Since on MacOS we can't download drivers from the GPU maker, we have to wait for Apple to eventually fix their driver bugs.
Photo of Ray Ketchem

Ray Ketchem

  • 36 Posts
  • 0 Reply Likes
Always the other company's fault right?
Photo of Ray Ketchem

Ray Ketchem

  • 36 Posts
  • 0 Reply Likes
Maybe I'm in the wrong thread. Point me to a thread that deals specifically with the cursor disappearing on an iMac running ML with CS6...
Photo of Chris Cox

Chris Cox

  • 20280 Posts
  • 848 Reply Likes
When the fault is in the other company's code - yes, then it is the fault of that other company.
If the fault were in our code, we would have said so and fixed it.

And please see the title of this topic.
Photo of Ray Ketchem

Ray Ketchem

  • 36 Posts
  • 0 Reply Likes
I can see the title of the thread. Thanks. Perhaps you could contact Apple on our behalf?
Photo of Chris Cox

Chris Cox

  • 20280 Posts
  • 848 Reply Likes
We filed this with Apple quite a while back. But they don't always listen to us, and respond better to pressure from customers. (heck, many of our bug reports have gone unfixed for years.. after Apple acknowledged them as bugs)
Photo of Mark Lee

Mark Lee

  • 83 Posts
  • 5 Reply Likes
Chris, you make it sound like Apple is the evil here. Just FYI: your customers don't (and shouldn't) care who's bug this is. When you release a product and charge money for it (a ridiculous amount of, I might add), which contains a major bug in it -- which you are aware of prior the release -- the fault is completely yours. You are too greedy to pull the product off. You have already made annual sales plans.

No product can cost this much if it's not tested properly. And no product of this magnitude can be written and tested properly within a designated timeframe (especially when it's only a year and most of your developers don't even speak english). Again, greed that leads to customers suffering.
Photo of Mark Lee

Mark Lee

  • 83 Posts
  • 5 Reply Likes
It would be the same if BMW started blaming Continental or Goodyear for crooked tires, instead of testing them properly before delivering their cars to the retailers.
Photo of howe roger

howe roger

  • 15 Posts
  • 2 Reply Likes
Corel . . . . A cheaper yet worable alternative!
Photo of Chris Cox

Chris Cox

  • 20280 Posts
  • 848 Reply Likes
When Photoshop was released, the OS was working. Apple later released an OS that contained bugs, but hasn't fixed those bugs yet. How is that Adobe's fault?

How could Adobe test for an OS that wasn't available at the time the Adobe product was written?

I understand that you don't like this OS bug, but there is little Adobe can do to make Apple fix their bugs. If you would like to see this OS bug fixed, please let Apple know that. Then perhaps Apple will give this bug in their OS some attention and get a fix out sooner.
Photo of Chris Cox

Chris Cox

  • 20280 Posts
  • 848 Reply Likes
Bad analogy. It's more like BMW shipped their car, then 6 months later Goodyear shipped a bad load of tires and kept shipping those tires after learning that they were defective. The design and testing of the car is really not involved in the issue.
Photo of Mark Lee

Mark Lee

  • 83 Posts
  • 5 Reply Likes
CS6 and Mountain Lion were available in beta the same time. In fact, Mountain Lion beta became available a whole month before CS6 beta.
Photo of Mark Lee

Mark Lee

  • 83 Posts
  • 5 Reply Likes
Chris, BMW don't ship their cars without tires. At least not in my country.
Photo of Mark Lee

Mark Lee

  • 83 Posts
  • 5 Reply Likes
In any case, this bug has been reported prior the CS6 release, no matter what analogy we use. I can believe you personally, or the developer team, didn't have a chance to see such reports, but that doesn't change the fact that someone on Adobe team chose to ignore it.
Photo of Chris Cox

Chris Cox

  • 20280 Posts
  • 848 Reply Likes
Mark - ok, you get good tires with the BMW and replace them defective ones several months later. Still doesn't involve the car.

And we filed a bug with Apple about Mountain Lion, but it is up to Apple to fix bugs in their OS (especially ones that can't be worked around).
Photo of Mark Lee

Mark Lee

  • 83 Posts
  • 5 Reply Likes
Chris, but I didn't buy any tires afterwards. I only bought the car with the tires it came with. Yes, I now realise the analogy wasn't great, because CS6 didn't come bundled with Mountain Lion.

But it has been in development the same time as Mountain Lion. I personally filed a bug report regarding this issue before both ML and CS6 were released.

Even if it was a last minute bug on ML's part, I can't believe Adobe didn't see this coming. I mean, how many parts of Photoshop's code are still not optimised for Cocoa, honestly? Illustrator still uses VJM, for Christ's sake. I'm more than sure Photoshop has some unoptimised parts, too.
Photo of Chris Cox

Chris Cox

  • 20280 Posts
  • 848 Reply Likes
Mountain Lion shipped after CS6. We filed the bug, and asked Apple to fix the bug. That's all we could do. Apple is responsible for Apple's code.
Photo of Mark Lee

Mark Lee

  • 83 Posts
  • 5 Reply Likes
Did you file it before CS6 was shipped?
Photo of Chris Cox

Chris Cox

  • 20280 Posts
  • 848 Reply Likes
When the bug was filed doesn't matter (and I don't know for sure). Only Apple can fix the bugs in Apple's code.
You're still working really hard to blame the wrong party here.
Photo of Judy Gulbis

Judy Gulbis

  • 1 Post
  • 0 Reply Likes
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!!
Photo of David

David, Official Rep

  • 3336 Posts
  • 541 Reply Likes
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.
Photo of Howard Gleichenhaus

Howard Gleichenhaus

  • 2 Posts
  • 0 Reply Likes
Every time I upgrade my Apple OS something doesn't work in Photoshop. Sometimes it's a filter sometimes an entire suite of filters.
Photo of Ray Stofberg

Ray Stofberg

  • 34 Posts
  • 2 Reply Likes
This issue is now already 5 months there. I don't care who is to blame. I paid over 1K in euros for the CS6 master suite. I use it everyday and am confronted with this issue everyday. it is costing me time and therefore money (way more than the amount I paid for CS6). It is aggravating and diminishes the pleasure in my work.

I fear this will never get solved and hopefully Adobe is capable of making a work around in CS7. Meaning I need to pay another 1K in euros to get something solved that should have worked properly in the first place.

BTW, this issue is ONLY with Adobe software at least on my machine. That makes me really suspicious about where the issue actually is.

If it is really Apple I find it amazing Adobe has not been able to generate enough attention from Apple to get it fixed after 5 months!!!!
Photo of Ray Ketchem

Ray Ketchem

  • 36 Posts
  • 0 Reply Likes
I agree.
Photo of Jon Cunningham

Jon Cunningham

  • 3 Posts
  • 0 Reply Likes
I also agree. Why do our cursors not disappear anywhere but in Photoshop? This is the only bug that has affected me in using Mac OS 10.8.2, that I know of.
Photo of Chris Cox

Chris Cox

  • 20280 Posts
  • 848 Reply Likes
Again, other users have seen this in many other applications - please see the other discussions on other sites: it is a common problem.
Photo of howe roger

howe roger

  • 15 Posts
  • 2 Reply Likes
I know I solved my problem by reverting to snow leopard but for your interest I was on a skype video call the other day whilst illustrating in photoshop and hey presto my cursor disappeared! Maybe this points to an Apple video card problem?

Anyway when just using photoshop all is fine.
Photo of Justin Coombs

Justin Coombs

  • 6 Posts
  • 0 Reply Likes
yup this is also happening to me. Running mountain lion - and it really only happens when I am using my tablet.

A restart fixes the problem, so it is something within Adobe Photoshop.

CS6 - you are the bane.
Photo of Talos Tsui

Talos Tsui

  • 11 Posts
  • 1 Reply Like
I was on Lion and I am having this problem. CS4 and CS5 were all running fine on my iMac with Lion (not Mountain Lion). As soon as I upgrade to CS6, I am getting disappearing cursor.

I tried delete Flash as some suggested. Still happening multiple times every day I am using CS6. I tried a beta version of Wacom tablet driver. Still not it.

So it is not Lion for sure! Since nothing got upgrade for our production machines during this period, it is CS6's doing. We have multiple Mac's and most (if not all) are having this problem.

Talos
Photo of matthew Peyton

matthew Peyton

  • 7 Posts
  • 0 Reply Likes
I had the problem with CS5 on Mountain Lion, Talos. Upgraded to CS6 hoping it would go away!
Photo of George Middleton

George Middleton

  • 4 Posts
  • 1 Reply Like
This happens on my system as well running Mac OSX 10.8.2 with an ATi Radeon HD 5870 1024MB (ATI5000Controller.kext 8.0.61) in a Mac Pro 5,1.

The cursor usually disappears after working in PS for some minutes, and seems to most often occur working with larger brushes. This occurs in PS CS5 as well as PS CS6. Also, it may or may not be sometimes accompanied by a loss of response of keyboard shortcuts for some panels, which may or may not be related.

For me, the problem is fixed temporarily by switching to the Finder or some other open application, then switching back to PS; the cursor then behaves normally for awhile, which might be a short time or longer..

The onset of the behavior and a return to normal seem somewhat random- tho it does seem to require switching out of the program and back to fix..
Photo of matthew Peyton

matthew Peyton

  • 7 Posts
  • 0 Reply Likes
Had my first Lightroom disappearance today. New mac hex core 32 gigs OSX 10.8.2 LR 4.3. Was working the crop tool - suddenly no cursor. I have tried the following this week: Increasing the default cursor size, replacing the (new) ATI Radeon 5770, updating from CS5 to CS6, running all updates Adobe and Mac. CAN I GET A LITTLE SUPPORT FROM ADOBE HERE THIS IS GETTING SILLY.
Photo of Chris Cox

Chris Cox

  • 20280 Posts
  • 848 Reply Likes
Please read the previous comments - this is a known issue in MacOS 10.8, and we're all waiting on Apple to fix it.
Photo of Ray Ketchem

Ray Ketchem

  • 36 Posts
  • 0 Reply Likes
I subscribe to Adobe Creative Cloud for the monthly fee.
I tried calling Adobe tech support about this. I was on hold for OVER AN HOUR when a support agent came on the line and apologized saying that my call had been routed to the wrong area.
I stayed on hold SECOND HOUR.

I finally gave up.

Shame on Adobe.
Photo of Ray Ketchem

Ray Ketchem

  • 36 Posts
  • 0 Reply Likes
Write a comment...
Photo of Ray Ketchem

Ray Ketchem

  • 36 Posts
  • 0 Reply Likes
No responses from Chris Cox for 3 days.
Photo of Chris Cox

Chris Cox

  • 20280 Posts
  • 848 Reply Likes
What is there to say? We're still waiting for Apple to fix their bugs.
Photo of matthew Peyton

matthew Peyton

  • 7 Posts
  • 0 Reply Likes
Thanks Chris - wasn't sure who's an employee who's not - new to the forum. Burning in a new Hex Mac this week - this was the number one bug (but not the only bug). Looks like I gotta wait. At least Apple got me a new Radeon 5770 really fast - that was a weird bug too - card kept 'rebooting'. Anyhow, please give my (Peyton)'s best to John Nack? (old team mate). Peace....
Photo of Kemper Fant

Kemper Fant

  • 6 Posts
  • 0 Reply Likes
Well, Chris...this is what I have to say to you and Adobe. If indeed you are waiting on Apple to "fix their bugs" then Adobe needs to train its support personnel to properly explain this issue and ALSO blame it on Apple. Of course, when I contacted Adobe about this issue, the technician seemed like he had never heard of it before and finally gave me some useless remedy for the problem. He also noted that they no longer supported 5.5 and suggested I upgrade to 6...which I did....which didn't help either. Amazing how Adobe is so certain that this is an Apple issue yet remains so unprepared for it when technical support is contacted. Doesn't exactly give you a lot of cred.
Photo of Ray Ketchem

Ray Ketchem

  • 36 Posts
  • 0 Reply Likes
This is happening with ADOBE software. It IS ADOBE's problem. If your software isn't working correctly YOU need to contact Apple and insist they fix the bug. This should NOT be an end-user's problem to solve.
Photo of Chris Cox

Chris Cox

  • 20280 Posts
  • 848 Reply Likes
Unfortunately, our outsourced support personnel are not always up to date.

Ray - sorry for the grammar snafu, I'll go fix that.
And I'm not a support employee, I'm a senior engineer writing Photoshop. I just answer customer questions while waiting on other things (like compiles, or an IDE to relaunch after yet another crash due to bugs in the debugger).

This happens in multiple applications, and is due to a known bug in the MacOS software. There is nothing we can do to work around it, and we, like you, must wait for Apple to fix the bugs in Apple's software. We have contacted Apple, but we cannot make Apple fix their (many) bugs. If you have some way to make Apple fix their bugs faster, we'd love to hear it. But so far the best known method to make Apple pay attention to bugs is for end users to tell Apple that the bug is important and that the users would like Apple to fix it soon.
Photo of Mark Lee

Mark Lee

  • 83 Posts
  • 5 Reply Likes
Chris, could you name at least one more of those "multiple" applications this happens in?
Photo of Mark Lee

Mark Lee

  • 83 Posts
  • 5 Reply Likes
Weird, but I've been using those apps everyday since the day ML came out and have yet to encounter cursor disappearance.
Photo of Ray Ketchem

Ray Ketchem

  • 36 Posts
  • 0 Reply Likes
I use all of those programs, but only have the cursor problem with Adobe.
Photo of Ray Ketchem

Ray Ketchem

  • 36 Posts
  • 0 Reply Likes
Chris, have you read all of the above posts? Many people are saying this only happens with Adobe and some are not using ML.
Photo of Chris Cox

Chris Cox

  • 20280 Posts
  • 848 Reply Likes
Yes, I've read them all. There are other causes known in older OS versions (usually due to cursor scaling or gestures). The vast majority of problems we're seeing are on 10.8 only, which is why the topic title was made more specific.
Photo of Mark Lee

Mark Lee

  • 83 Posts
  • 5 Reply Likes
You are avoiding the question.
Photo of Ray Ketchem

Ray Ketchem

  • 36 Posts
  • 0 Reply Likes
I understand Chris. But what, if anything is Adobe doing to help get this fixed? Are you saying there is NOTHING that you or Adobe can do?
Photo of Chris Cox

Chris Cox

  • 20280 Posts
  • 848 Reply Likes
After reporting the bug to Apple and asking repeatedly that they fix the bug - no, there isn't much more we can do. If this was a frequent crash or data loss, we could escalate it to the executives ... but this is just an annoyance. And we have a lot of other higher-priority bugs that Apple needs to fix (many that do involve crashes or data loss).

So users need to let Apple know that this is important to them, in order to raise the priority of the bug within Apple.
Photo of Ray Ketchem

Ray Ketchem

  • 36 Posts
  • 0 Reply Likes
This is far more than an annoyance. I'm an illustrator that uses Photoshop to make a living. This bug has cost me time, which is money to me. For the price that Adobe is charging for Creative Cloud, this bug is absolutely unacceptable. Continuing to blame Apple, while offering no solution is VERY frustrating. Especially considering Adobe support is so terrible that I had to hang up after waiting two hours.
Photo of Ray Stofberg

Ray Stofberg

  • 34 Posts
  • 2 Reply Likes
My cursor disappears every 10 minutes forcing me to exit the program, distracting me from my work. This is costing me daily my time. Not sure how much time, next to the distraction and annoyance.

I am flabbergasted this is apparently not yet escalated to the Apple executives by Adobe. What will do this??? A claim by Adobe users for time lost and suffering??

This so-called mere 'annoyance' is actually having an impact on the very core of my work. I really call it more than an annoyance. If ai can choose having CS6 crash on me once a day or this I would happily take the daily crash.
Photo of Chris Cox

Chris Cox

  • 20280 Posts
  • 848 Reply Likes
Again, we cannot solve Apple's bugs. I'm sorry that Apple's bugs are unacceptable to you. But we simply cannot fix Apple's bugs, and although we can file bug reports with Apple, we have little leverage to make them fix their bugs. This has nothing to do with the price of the creative cloud or Photoshop - because this is an unavoidable bug in Apple's OS. We can't work around it, and we cannot offer a solution to this OS bug. And Adobe support can do even less about Apple's bugs.

In the list of MacOS bugs, this is just an annoyance, and far from the most critical.

Again, you need to let Apple know that this is a problem. We've done what we can. But Apple needs to understand how important this is to you, so they can prioritize fixing their code.
Photo of Mark Lee

Mark Lee

  • 83 Posts
  • 5 Reply Likes
Yet you find it acceptable to release your product when you know this bug will be there.
Photo of Chris Cox

Chris Cox

  • 20280 Posts
  • 848 Reply Likes
When we released Photoshop CS6, MacOS 10.8 was not yet available.

Even if it was available, how would an unavoidable bug in MacOS affect the release of Photoshop?
Photo of Ray Stofberg

Ray Stofberg

  • 34 Posts
  • 2 Reply Likes
Chris,

I am not asking you to fix Apples bugs. I do expect Adobe to escalate this until it does get fixed. I am amazed this is apparently still at a lower level.

I wonder how many people in Adobe actually use their own product multiple hours a day drawing for their income? I am pretty sure they will come to the same conclusion. This might seem a minor bug to Apple but for working with PS this is horrible.
Photo of Ray Stofberg

Ray Stofberg

  • 34 Posts
  • 2 Reply Likes
Yes, I did report this to Apple too but as a professional user of PS that is affected by this I am sure I am such low percentage that my scream for help is barely heard. I am pretty sure I am in a larger percentage to Adobe.
Photo of Chris Cox

Chris Cox

  • 20280 Posts
  • 848 Reply Likes
The Photoshop team uses the product quite heavily (not just for development). But most haven't moved to 10.8 for anything more than testing, because 10.8 still has significant bugs.

If you believe this is important, please let Apple know that.
Photo of Talos Tsui

Talos Tsui

  • 11 Posts
  • 1 Reply Like
I don't understand why I have no problem with CS4 and CS5 on the same machine until I upgrade to CS6. What's changed in CS6 that reveal this bug in OS X 10.7.X or higher?

What is the radar related to this bug that was filed? Care to share, so that we can pile in on the bug?
Photo of Chris Cox

Chris Cox

  • 20280 Posts
  • 848 Reply Likes
We don't know what changed exactly, other than using more GPU features. Apple will have to tell us that once they have the cause of the bug identified.

We're not allowed to share RADAR information per NDA with Apple, and you wouldn't have access to the bug anyway (right now even I don't have access, it's in Apple's court).
Photo of Talos Tsui

Talos Tsui

  • 11 Posts
  • 1 Reply Like
They're not public. But sharing the number on Twitter gives a headsup to the people who work at Apple that folllow any devs on twitter. The actual radar number is not super useful for anyone outside Apple. But for anyone inside Apple, it's insanely useful.

There is OpenRadar, which people post stuff into if they want to make it public. And then link the radar number for other developer to dub. A community thing making it easier to see common complaints and sometimes get comments from people who've hit the same bug or whatever.

FYI, I have no problem with any other apps on this issue, only Adobe's CS6 under Lion 10.7.
Photo of matthew Peyton

matthew Peyton

  • 7 Posts
  • 0 Reply Likes
22 years using Macs and developing softs. No cursor issues any other aps but Adobe since ML upgrade two weeks ago....
Photo of matthew Peyton

matthew Peyton

  • 7 Posts
  • 0 Reply Likes
Sorry to beat a dead horse but just to add to the info had the cursor vanish in LR again using crop tool - this time the crop was frozen and I had to quit out and restart to finish the image edit. Seems this is a real 'hair bag', to quote an audio engineer I used to work with!
Photo of matthew Peyton

matthew Peyton

  • 7 Posts
  • 0 Reply Likes
Yeeeek this is the angry Pshop guy forum! Chris sorry I summoned you.

As a funny aside ML is the crash-iest OS I have seen on a Mac since beige Macs went away. Really, I have had two failed shut downs and one endless color wheel today on a brand new Mac brand new OSX with tons of RAM running stuff that's been stable since, well, OS Housecat or whatever.

Apple took it's eye off the ball once before, in my career, and I wound up with a closet full of IBM Thinkpads...
Photo of Chris Cox

Chris Cox

  • 20280 Posts
  • 848 Reply Likes
Official Response
This is a known bug in MacOS 10.8 that affects multiple applications.
(it happens to me most often in Safari, with no Photoshop running. And you can see a lot of reports of this in Apple's user forums.)

We have notified Apple of the problem, and are waiting for an OS fix from Apple. It is still unfixed as of MacOS 10.8.5.

Unfortunately, this is something that we cannot work around.

UPDATE - Apple fixed it in 10.9
Photo of matthew Peyton

matthew Peyton

  • 7 Posts
  • 0 Reply Likes
Chris I didn't mean you were angry..... :-) I appreciate your candid answers. Heck, this is my 9 billionth OS upgrade they usually take some burn in time...... Just hope OSX 10.8.3 runs a little less hurkyjurky. Anyhow thanks for taking heat here in the kitchen! Peace and I'm out.
Photo of Talos Tsui

Talos Tsui

  • 11 Posts
  • 1 Reply Like
Chris, I think Adobe should bump this bug from low priority to medium or higher priority within Adobe. It is affecting users who is using the app everyday. After endure this for over 3 months. People can lost their cool.

It will only get worst. An "annoyance" happens 10+ times a day over the course 3 months (work days only) is equal to 600+, that is no longer an annoyance. It is driving us crazy.

( Still don't understand why this known bug only happens in CS6, and not the other apps like you stated. )

Looking forward to switch to the new 27" new iMac...
Photo of Chris Cox

Chris Cox

  • 20280 Posts
  • 848 Reply Likes
Many people have seen it happen in other applications.
But if you use Photoshop most often, then that is where you are going to see the OS bugs most often.
Photo of Ray Ketchem

Ray Ketchem

  • 36 Posts
  • 0 Reply Likes
This is simply NOT TRUE in my case. It only happens within Photoshop.
Photo of Chris Cox

Chris Cox

  • 20280 Posts
  • 848 Reply Likes
Again, other users have seen it in many different applications. And that is true, as you can see from the other discussions previously linked.
Photo of Ray Ketchem

Ray Ketchem

  • 36 Posts
  • 0 Reply Likes
This doesn't mean it's even related. In my case this is clearly a Adobe problem.
Photo of Chris Cox

Chris Cox

  • 20280 Posts
  • 848 Reply Likes
No, it means that you have a very small sampling of the problem.
And since this is a known bug in MacOS that affects many application, it could hardly be an Adobe problem.
Photo of Talos Tsui

Talos Tsui

  • 11 Posts
  • 1 Reply Like
safari, MS office, iChat, On the Job and CS6 are all the apps I launched in the morning, and quit at 5pm. SO they were ALL being used everyday. But only CS6's cursor disappear. So it is not the case of "the other apps not being use less CS6 here".
Photo of Chris Cox

Chris Cox

  • 20280 Posts
  • 848 Reply Likes
I don't know - other users are seeing the cursor disappear in other apps. Again, you only have a small sampling of the problem (a sample size of one, out of millions).
Photo of Liora Blum

Liora Blum

  • 7 Posts
  • 0 Reply Likes
I agree with Talos. It is obviously a low priority for both Adobe and Apple, and should be seen as a high priority. It is also driving us all crazy.

A few months ago, I offered to contact Apple and Adobe on behalf of people from this list. I didn't receive enough responses, but if Photoshop users write to me (info@dynamicbrushes.com), I will write a petition and send it to both Apple and Adobe.

I also called both companies and waited for over an hour for both companies. I was put through to tech people who knew nothing about the issue with the cursor, and had never heard any complaints about it. I begged the Apple guy to tell his superiors.

As someone wrote in this thread, we are screaming for a solution and no one can hear us.
Photo of Chris Cox

Chris Cox

  • 20280 Posts
  • 848 Reply Likes
Please let Apple know that you consider it a high priority. Adobe can't do much more about Apple's bugs.

Petitioning Adobe won't fix Apple's code.
Photo of Talos Tsui

Talos Tsui

  • 11 Posts
  • 1 Reply Like
we can't tell apple to fix this bug without knowing the radar #. That is the best way to reference them. Since all the technical details are all listed in the radar.
Photo of Chris Cox

Chris Cox

  • 20280 Posts
  • 848 Reply Likes
You can tell them, but I cannot give you the RADAR number.
Photo of Ray Ketchem

Ray Ketchem

  • 36 Posts
  • 0 Reply Likes
We (Adobe users) are obviously getting nowhere by telling Chris about this problem. It is falling on deaf ears.

Is there a supervisor of Chris who reads these comments? If so, please speak up.
Photo of Chris Cox

Chris Cox

  • 20280 Posts
  • 848 Reply Likes
I'm sorry that you are frustrated, but complaining to Adobe about an Apple bug really is not productive.

Please let Apple know that you would like to see this bug fixed in their OS.
Apple is the only party that can fix bugs in Apple's OS.

If this really disturbs you that much, you can reinstall MacOS 10.7 until Apple fixes the bugs in 10.8.
Photo of Ray Ketchem

Ray Ketchem

  • 36 Posts
  • 0 Reply Likes
It's unclear to me why you continually insist that this is not your problem. ADOBE users are angry and frustrated. YOUR software doesn't work properly in one of the major computer operating systems. YOU should be telling us how YOU are working with Apple to find the bug. Instead you sit back and say, "Not our problem"?
Photo of Chris Cox

Chris Cox

  • 20280 Posts
  • 848 Reply Likes
Yes, I understand that you are frustrated by the Apple OS bug. But we're just as much a victim of the OS bug as you are. Apple is responsible for Apple's code, and only Apple can fix bugs in Apple's OS. We have worked with Apple, but as I've already explained many times: we cannot make Apple fix their bugs. All we can do is notify Apple of their bugs, and ask Apple to fix them. We cannot force them to fix their bugs, and we cannot fix their bugs for them. Sometimes we can work around their bugs, but in this case we cannot. Really, there's not much more we can do.

If you would like to see this bug fixed, please let Apple know that you consider this OS bug to be important.
Photo of Ray Ketchem

Ray Ketchem

  • 36 Posts
  • 0 Reply Likes
What is the most potent way of telling Apple how important this is?
Photo of Chris Cox

Chris Cox

  • 20280 Posts
  • 848 Reply Likes
File bugs and tell them how it impacts you.
Write on their forums, and tell them how it impacts you.
Give them some reason to prioritize this over all the other serious bugs they need to fix in MacOS 10.8.
Photo of Talos Tsui

Talos Tsui

  • 11 Posts
  • 1 Reply Like
Chris, since i am having this problem with 10.7 with only CS6, I should downgrade to 10.6 then?
Photo of Liora Blum

Liora Blum

  • 7 Posts
  • 0 Reply Likes
I only ever had the problem of a disappearing cursor with Photoshop, after I installed ML. When I spoke to the Adobe representative, they told me that I had to buy CS6 because CS5 was not compatible with ML.

I immediately went and bought CS6, hoping it would do away with the problem. I can report that the cursor disappears far less than it did on CS5, but it still happens often enough.

(I also have a MacBook Pro, and luckily I didn't upgrade to Mountain Lion there, so there is no disappearing cursor in Photoshop on that computer.)

I don't really care whose fault this is. Like everyone else on this forum, I am not able to work properly, and after paying for professional programs that have worked in the past, I expect them to work in 2013, too.
Photo of Chris Cox

Chris Cox

  • 20280 Posts
  • 848 Reply Likes
I'm sorry you got a bad support person and incorrect information.

But please let Apple know that you would like this problem fixed.
Photo of Chris Cox

Chris Cox

  • 20280 Posts
  • 848 Reply Likes
Disappearing cursors on OS versions prior to 10.8 tend to involve cursor scaling in the OS controls, accidental use of gestures, or accidental use of OS keyboard shortcuts that change app focus.
We had almost no reports of such problems until 10.8, and with 10.8 the cursors disappear in many applications without other factors (like the aforementioned causes) being involved.
Photo of Talos Tsui

Talos Tsui

  • 11 Posts
  • 1 Reply Like
Chris, could you explain what is a "cursor scaling in the OS controls"?

I do know "accidental use of gestures" and "accidental use of OS keyboard shortcuts that change app focus" are not the causes here, since we know what we doing.

Thanks.
Photo of Ray Ketchem

Ray Ketchem

  • 36 Posts
  • 0 Reply Likes
What are all these other "serious bugs" that you speak of?
Photo of Chris Cox

Chris Cox

  • 20280 Posts
  • 848 Reply Likes
The hundreds of RADAR bugs that we have filed on OS code crashes, file system problems that lead to lost files, OS memory leaks, etc. Those tend to be prioritized above "cursor sometimes disappears".
Photo of Philipp Ringli

Philipp Ringli

  • 2 Posts
  • 0 Reply Likes
This does also happen on Retina MacBook Pros with Nvidia graphics.
Photo of Jared Smoker

Jared Smoker

  • 1 Post
  • 0 Reply Likes
A restart won't necessarily fix the curser disappearance problem. I have not found a solution yet. My work-around is to zoom in a bit (control+scrolling). Zooming in a little with this Mac function causes the curser to reappear. Zooming back out to regular screen view will cause the curser to disappear again. I wish there was a fix to this problem, but this method or a quick swipe into MC and out again to bring it back is all I can do to cope.
Photo of Ray Ketchem

Ray Ketchem

  • 36 Posts
  • 0 Reply Likes
I spoke with Apple Care about this problem. Apple claims that the problem lies with the software developer. In this case Adobe.

The rep said think of it like this,
"We design the car, they design an accessory for the car. If their accessory doesn't work correctly it's not the fault of the car."

He also said,
"Software developers had Mountain Lion to work with months in advance of its release. If the developer didn't work out their bugs for the official release that's not Apple's fault."
Photo of Chris Cox

Chris Cox

  • 20280 Posts
  • 848 Reply Likes
You spoke to someone who has no idea what they are talking about.
In this case the car doesn't work to start with. This cursor bug affects MANY applications, across the OS.

And many bugs were filed during the Mountain Lion beta that still have not been fixed.

Please let Apple know that you are disappointed with their failure to fix their software, and further disappointed in their attempt to blame other parties for bugs that they have already admitted are in the OS.
Photo of Ray Ketchem

Ray Ketchem

  • 36 Posts
  • 0 Reply Likes
Actually it was a senior Apple supervisor who seemed to know exactly what he was talking about. He checked, while I was on the phone and he said Adobe had filed NO info about this bug.
Photo of Ray Ketchem

Ray Ketchem

  • 36 Posts
  • 0 Reply Likes
No comment from Chris on my above reply.
Photo of Chris Cox

Chris Cox

  • 20280 Posts
  • 848 Reply Likes
Sorry, didn't see your post. Also, he was quite wrong.
Photo of Ray Ketchem

Ray Ketchem

  • 36 Posts
  • 0 Reply Likes
Can you tell us, specifically, who you filed the support claims with? This 'he said, she said" is ridiculous.
Photo of TH

TH

  • 21 Posts
  • 1 Reply Like
My Apple senior tech friend Evan says he knows nothing about it.
Photo of Chris Cox

Chris Cox

  • 20280 Posts
  • 848 Reply Likes
We filed it in RADAR, like all other Apple bugs.
Photo of Terrence Seaford

Terrence Seaford

  • 12 Posts
  • 3 Reply Likes
This may be a solution. First, some background.
I experienced the disappearing cursor in CS5.5 after upgrading to 10.8 from 10.6. I reverted to Snow Leopard successfully. A couple of weeks ago I decided to give 10.8 another try. But this time I skipped upgrading over a Snow Leopard installation.

I backed up my boot drive, wiped it and then booted my 10.8 test installation from an external disk, restarted, and booted the Recovery partition. I installed 10.8 on my MBP's internal drive from the Recovery partition. I then restored my apps and files, after OS installation, using Migration Assistant.

After an hour of running small to large cursor exercises, Photoshop behaved as it should. No cursor issues. Last Friday I upgraded to CS6. So far so good.

So, upgrading over the 10.6 install may be the culprit, forcing the misalignment of ones and zeros that have caused so much pain and suffering. And if this "solution" continues to work, I'll likely tear everything apart and do a complete virgin install of everything from the ground up.
Photo of CityKitty

CityKitty

  • 1 Post
  • 0 Reply Likes
This sounds like a brilliant and sensible solution. I think I’ll do this 1st, as opposed to doing the upgrade over Snow Leopard.
Nothing like a clean install to do the trick.

Has anyone else tried this?
Photo of Chris Cox

Chris Cox

  • 20280 Posts
  • 848 Reply Likes
A few people have done a clean OS install and reported that cursors worked correctly (and other OS bugs got better). But we have not been able to confirm this.
Photo of Talos Tsui

Talos Tsui

  • 11 Posts
  • 1 Reply Like
Switch to all new 27" iMac. Problem solved. CS6 no longer give me the cursor problem like before with OS X 10.7. Work fine with OS X 10.8.X.

This conversation is no longer open for comments or replies.