P: Arrow key's stop working in type tool / text in CS6

Howdy Jason,

Just so you know, there have been some problems with various tablet devices on Mountain Lion, the version of Helevtica Neue which ships with the OS has had some problems, and Chrome can trigger keyboard interception as can other programs which "sit on top"/go semi-modal or monitor input. That said,
I'd like to follow up with you via a connect session, so we can get to the bottom of your problem. If we can isolate it within Photoshop, then we can fix it otherwise hopefully we can figure out a workaround.

Thanks,
David

I've read all the comments and have exactly the same problem. However, I've had CS6 installed for quite a while now and the bug only just started appearing after I uninstalled an old version of Growl. No idea if this is the cause or helpful at all?

Had the same problem with the unresponsive arrow keys, but restarting the open browser seemed to fix.

Details:
Photoshop CS6 Extended 13.0 x64
Safari 6.0 (8536.25)
OS X 10.8.1
13-inch, Mid 2012 MacBook Air, 1.8 GHz Intel Core i5, 8 GB RAM, Intel HD Graphics 4000 512 MB

I'm also having the EXACT same problem.

Brand new machine, MBP running Mountain Lion.

First time ever using CS6, first PSD from scratch in CS6, noticed this problem right away while running a bunch of other crap.

Went back, tested, closing things arbitrarily and tested again to reproduce the problem. I was able to see the problem go away by some of the following: >> Closing Firefox, Closing Microsoft programs, Saving the File within PS CS6,

Short of it is this: it's not consistent.

I can boot up from dead, with a couple of things running in the background. Dreaded Symantec Antivirus. A Novell client for some shared drives. That's it. And still reproduce the problem while running only Photoshop.

A sequence of operations that I've performed to BOTH produce it and not produce it: >>

Open Recent> select file
Move tool> Select Text Box Layer
Nudge>Keyboard Arrow Up>nudge nudge nudge
"T" Text Tool
Click Select anywhere in the same text box.
Keyboard arrow to Navigate the Paragraph is non responsive. Cursor remains still.

Sometimes I may change the leading or kerning on a line of text and then try to unselect it by the arrow key, and it will have become non-responsive.

Sometimes the behavior will appear only after I've selected several text boxes and modified text at least one of them.

The font for this file is, indeed, Helvetica Neue, but it came with the install, I thought? It's also the standard publication font for my work, so, I can't delete it. Nor can I disable Symantec. Nor can I downgrade from Mountain Lion.

I have an NVIDIA GeForce GT 650M Graphics Processor, which I disabled, by unchecking the GPU box. But I can still reproduce the problem and it sucks.

My personal workaround is going to be InDesign, for whatever I do next with heavy text, with the hope that this problem is limited to PS and not CS6 broadly.

Unfortunately, I don't have that setup as I was helping a user via a connect session. There is a command under the preferences which takes control of keyboard shortcuts. When we tested it, there seemed to be a lag when that command was enabled. If you would like, I can try and walk you through it via a connect session today. I'll follow up with an email.

Thanks,
David

Can you specify which Magic Mouse settings?

Howdy Imran,

Did you read the previous comments? Are you running Chrome? Are you using a Magic Mouse? Have you checked your third-party pointer/mouse/keyboard utilities. We've heard about this problem several times, but each time the cause has been one of these. If you have clear steps indicating Photoshop, however, we'd be happy to walk through it with you.

Thanks,
David

Specifically, try closing Chrome.

I've already heard a couple of complaints about the Magic Mouse. There are some settings which take control of keyboard input which cause problems for Photoshop as well as other applications. If you would like, I can walk you through it via a connect session.

Thanks,
David

Are you committing the resize of the text? If not, then the app is in a modal state and not responding to the same keyboard commands as normal, but rather those keyboard commands that deal with the transform (resize) which you initiated but did not complete.

Thanks,
David