P: CS6 / CC Keyboard shortcuts not responding Mavericks/Yosemite MacOS 10.9; 10.10

Hi Adam,

While I understand your view that this is a joint problem or even that you feel any fault with Adobe software must be Adobe's problem, try to see it from the perspective of those who develops software.

The company that makes the operating system, whether Windows or Mac OS or Linux or whatever has certain specifications, much as highways do. Now, companies that create software for these operating systems then rely on the manufacturer to actually live up to their own specifications, much as automotive manufacturers rely on the government to make roads to a certain width, thickness, smoothness, etc based on their specs. So far, so good...

What would happen to car manufacturers if suddenly the specifications for roads change arbitrarily? Perhaps, without any warning, they became 10" more narrow or required special tires or could only be used in Fall or dissolved in the snow. Would it be reasonable for the auto manufacturers to predict such a sudden and expected deficiency AND (turning on a dime) design new cars to compensate for these design flaws AND (at no additional cost) still support all the roads without such a flaw? Well, that's sort of what you're implying. It's the responsibility of the road manufacturer to live up to their spec and it is the responsibility of the OS manufacturer to produce OSes that live up to their system specs.

Sure, OSes change. And such changes are generally announced for the above reasons. I mean, in an ideal world, the OS company WANTS software to work on their OS, so it's in their best interest to communicate changes to everyone. You may remember a certain lawsuit against a Redmond company for violating this principle to give their own software an advantage...

My point? It ABSOLUTELY matters where the bug arises. If the OS has a flaw preventing certain things (like driving in the rain), there is NOTHING we can do about it. Even if we had some magical patch to the OS, it is actually ILLEGAL for us to change their code or supply a fix to users. On the other hand, if the bug is with our code, the same applies and Apple cannot make changes either. This equally applies to Microsoft, Wacom, Sun, Quicken, IBM, Qualcomm, McAfee, etc.

At this time, we have still not isolated why the bug ONLY happens on Mavericks and not earlier versions of Mac OS. We work with Apple constantly on such issues. We are still actively investigating and gathering information (I'm on this thread several times a week, at least!). I don't know what further transparency we can give or could be reasonably expected. Meanwhile, please look at the different corporate responses and levels of customer engagement on this issue, as you point out in #1, and I think you can answer your own question about who is being transparent and communicating and who is basically ignoring the issue for customers.

Thanks,
David

We are continuing to work with Apple on this and a number of other issues related to MacOS 10.9.

If the bug is in Apple's code, it is Apple's responsibility to make their code work correctly. Expecting third parties to work around defects in the OS is beyond ludicrous (and we already have to work around a lot of as-of-yet-unfixed defects in the OS).

At this point we still don't know what is causing this particular issue - so there is not much we can say.

Chris, thank you very much for your response to my post above. I hope you or another adobe representative could clarify a few points for those of us still dealing with this very obstructive bug.

1) Can you confirm or deny whether there is an ongoing dialogue between Apple and Adobe regarding this issue?

Frustratingly, apple does not have a channel for end users to log concerns arising from incompatibilities between their OS and third party software. As of yet, no apple customer service representatives or engineers have weighed in on this issue in any of the apple support posts, and CSR's approached over the phone refuse to address any issues concerning third party software.

2) "So far, this seems like an Apple or Adobe issue [...]" To be clear, I understand that in context you merely meant to say it does not seem like a "Wacom issue". But when it comes to Adobe versus Apple... does it matter?

Here's the thing: I'm trying my best to remain thoroughly impartial, but everything I've been hearing from Apple CSRs (two lengthy phone conversations and counting) seems to indicate that it doesn't matter whether the issue arrises from a bug in adobe code or a bug in Mavericks; from their perspective, it is Adobe's responsibility to QC and fix their own third party software.

3) When will the Mavericks compatibility FAQ be changed to reflect this issue which you agree is likely caused by Apple or Adobe code; or, do you not acknowledge this is a "significant issue"? I feel that when users like James are calling for "more transparency", what they are really asking for is a formal acknowledgement of the issue and a statement of intent to fix it. I don't see what harm could possibly be done by doing everything you can to inform your customers of your awareness of this issue, and updating this FAQ would be a good gesture.

http://helpx.adobe.com/x-productkb/gl...

Finally, I want to say something to the rest of the community participating in this thread. For one thing, assuming that this issue is caused *exclusively* by a bug in Mavericks OS coding because PS CS6/CC work fine on the Mountain Lion OS is flawed, for the same reason that one cannot assume the fault lies *exclusively* on adobe because CS4/CS5 work fine on the Mavericks OS. Lets refrain from finger pointing and try to remember that we have received every indication this error is generated from an incompatibility between CS6/CC and Mavericks, meaning the fault exclusively lies with neither party.

Ben,

Another way of bringing the keyboard back to life is to click on the interface's panels . I have to do it all the time now : (

I encountered this issue only after upgrading to Maverick. I use [ & ] keys to change brush size and I must paint another stroke before the shortcuts begin to work. Super annoying.

I can replicate this most times I use the brush tool.

Thank you. Glad to know I'm not the only one with this problem. Hoping its solved soon.

Yes, it is very much related to MacOS 10.9.

Ever since I updated my Mac to 10.9.1, photoshop CS6 has been freezing sporadically. If I'm using the brush and use a keyboard shortcut to switch tools it doesn't register until I click the tool. If I switch applications and go back to photoshop it doesn't register until I switch to open applications a bunch of times and then go back to photoshop. Not sure if this is related to the Mac update or not.

thx Lukasz, I've closed Painters Wheel and it's better now, but still some problems. Anyway I think it resolved lasso tool problem.

I have now this same problem
But only when I use plug in:
with Coolorus plug in: after sumpling color from coolorus panel, many shourtcuts don't work (cmd+z, opt+backspace and more) when I switch to other application, and return to photoshop - everything works fine - as long as I choos other color from coolorus panel.
I tried other color wheel plug in - Painters wheel. Difrence is, that now less shortcuts dont' work: cmd+z works but for example opt+backspace doesn't.
when not using plugins - everything works fine and no problem with short cuts.

Maby it will help someone to find solution for this.