Keystrokes lost since upgrading to Lion

Run "Activity Monitor" and ask it to display disk activity.

This way, you will be able to check if the app write on disk when the keys are on strike.

It's to get rid of this kind of behavior that I wrote a script giving us a clone of the defunct Save As.

Peggy encapsulated it in a Service allowing us to trigger it with a shortcut.

Yvan KOENIG (VALLAURIS, France) lundi 10 octobre 2011 11:16:07

iMac 21”5, i7, 2.8 GHz, 4 Gbytes, 1 Tbytes, mac OS X 10.6.8 and 10.7.0

My iDisk is : <http://public.me.com/koenigyvan>

Please : Search for questions similar to your own before submitting them to the community

I can not see clear correlation between autosaving and keystroke problems. Even so it is frustrating becasue you are not sure you copied something or not.

Krzysztof

It's really simple and has no relation to data loss. I repeat that on a clean system, the autosave feature do its duty correctly.

When the app is saving, it 'eat' much processor cycles. This may explain why the key stroke aren't treated.

I highlighted the word may because it's just an hypothesis.

It's just difficult to assume that a behavior reported by less than ten users may be a bug in the system or even in a given app.

Yvan KOENIG (VALLAURIS, France) lundi 10 octobre 2011 13:41:16

iMac 21”5, i7, 2.8 GHz, 4 Gbytes, 1 Tbytes, mac OS X 10.6.8 and 10.7.0

My iDisk is : <http://public.me.com/koenigyvan>

Please : Search for questions similar to your own before submitting them to the community

If this hypothesis is true how to explain that cmd-c does not work but mouse with choosing "copy" from menu works OK?

Krzysztof

If it's not the Autosave task which stop temporarily the process, you must search wich is the extraneous piece of software which plays the fool.

I baught Lion one week after it's delivery and since, I use Pages and Numbers at least half a day.

Everything behave well.

But as I am always playing safe,

I installed the system on a blank HD then added only iWork and worked this way during three weeks.

Doing that, I'm sure that iWork apps are behaving flawlessly on Lion.

Given that, Apple isn't responsable of every third party products which you may have installed.

Yvan KOENIG (VALLAURIS, France) mardi 11 octobre 2011 12:27:02

iMac 21”5, i7, 2.8 GHz, 4 Gbytes, 1 Tbytes, mac OS X 10.6.8 and 10.7.0

My iDisk is : <http://public.me.com/koenigyvan>

Please : Search for questions similar to your own before submitting them to the community

Has anyone yet tried uninstalling iWork or Pages and install it again??? It has solved other problems with iWork and Pages for people on Lion.

Yes. I did that and it did not fix the bug.

Reinatalling did not fix my situation.

And I do not have any hacks or odd system fixes running.

S

Yes, USA, standard American English keyboard.

I'm having the same or a similar problem. I was hoping that the latest update to OS X would fix this but it may be worse than before the update. I'm using a 17 MP Pro and the problem occurs on the laptop keyboard or an external full size wired aluminum keyboard. Very frustrating.

On the right side of the wireless keyboard there is a power button. I've replaced the batteries and the problem still happens.

I've seen that others have this problem with wired kb. It does "act" like the keyboard has gone to sleep or something because pressing the power button on the side has an instant affect of making the keystrokes work again. But it comes back.

I've seen somewhere else where someone said maybe the mac is busy with cache or something and I don't think that's the case because cut/paste will work instantly if you use the mouse and select the menu options. They just don't work from the keyboard.

I've also had instances where no keystrokes respond when I'm using Numbers. Not just the CMD keys but anything I type.

It's very frustrating with it's apparent irregularity but there is no doubt pressing the power button instantly resolves each occurrence for me.

this thread thinks it has a solution...

command+c doesn't work ~ Snow Leopard

I didn't have VoiceOver turned on but as the article suggested I turned it on and back off again.

I tested it out in Pages and didn't have a problem just now but this has been such an intermittent issue that I think it will take a few days to know for sure if this fixed it

Before reinstalling iWork you have to certain you have uninstalled all important parts, not just the iWork folder with its applications.