Macbook Pro random "stuck" keys under Leopard

[CoolHandPete]

I realize there is a widespread problem with unresponsive keyboards under Leopard, but this is not the same issue.

With a 2.4 MBP w/4 GB RAM:

On occasion, after installing Leopard, upon waking from sleep, my keyboard will suddenly register a key as being permanently pressed, resulting in an inability to do much of anything except listen to the repeated bebebebebebeep of a key pressed incessantly. Sometimes it's the shift key; other times it's a number key, or the Apple key. It has been the semicolon key, the "p" key, and the Tab key. When I open the Keyboard Viewer, it shows which key or keys are being registered (thanks Tech support for showing me that feature). When I sleep the computer again, it sometimes stops once I wake it up again. Other times, it will quickly start happening again and will take another sleep-wake or a restart to function normally.

During all of this, the trackpad seems to function normally.

It doesn't seem to have increased in frequency, though the first few days it happened (around 11/6) it occurred 10x or more per day. Now, it seems to occur about 3-4x every few days.

The keyboard is functioning normally otherwise, and the hardware seems to be fine. (Read: there are no ACTUAL stuck keys!)

I understand it's unlikely anyone will be able to solve this problem, but I'd sure love to know if anyone else is experiencing this after upgrading to Leopard.

Best,
Peter

[1337_5L4Xx0R]

Negative.

[DrSly]

Hello,

Same issue here, have been looking to solve this for a while. Although my Macbook Pro is very recent (mid-October), the problem appeared after I installed Leopard, but not right away.

I log in, and the little login window "shakes" and you can hear a beep-beepbepbeep-beeeeeeeeeeeeeeep as if some keyboard input was repeated endlessly. It happens even sometimes after I do manage to log in (by frantically clicking on the "back" button with the mouse on the login window, sometimes it works, sometimes I have to put the machine to sleep...) Sadly, I cannot predict when it will happen, as it sometimes behave perfectly.

So it doesn't happen all the time, just about half the time, and I won't speculate on whether it is a hardware or software issue, it is too hard to assess at the moment, since I use many different peripherals in conjunction with the Macbook Pro, such as Bluetooth wireless mouse and keyboard from Apple, and external monitors (many). The problem happens sometimes when such peripherals are enabled and plugged, sometimes not, sometimes without them, sometimes not...

another link found on the web with the same issue:http://www.techsupportforum.com/alte...petitions.html

I will be posting on the Apple Discussion forums about this too.

Very frustrating.

:-(

Any feedback, ladies and gents?

Thank you

Dr Sly

[Karelia]

I have one answer for both of you, and it seems to resolve most all Leopard-related quirks.

Reinstall Leopard.

[funkydata]

So did you find a cure? My macbook pro (less than 2 months old) did the same thing for two hours yesterday.

Originally Posted by DrSly

Hello,

Same issue here, have been looking to solve this for a while. Although my Macbook Pro is very recent (mid-October), the problem appeared after I installed Leopard, but not right away.

I log in, and the little login window "shakes" and you can hear a beep-beepbepbeep-beeeeeeeeeeeeeeep as if some keyboard input was repeated endlessly. It happens even sometimes after I do manage to log in (by frantically clicking on the "back" button with the mouse on the login window, sometimes it works, sometimes I have to put the machine to sleep...) Sadly, I cannot predict when it will happen, as it sometimes behave perfectly.

So it doesn't happen all the time, just about half the time, and I won't speculate on whether it is a hardware or software issue, it is too hard to assess at the moment, since I use many different peripherals in conjunction with the Macbook Pro, such as Bluetooth wireless mouse and keyboard from Apple, and external monitors (many). The problem happens sometimes when such peripherals are enabled and plugged, sometimes not, sometimes without them, sometimes not...

another link found on the web with the same issue:http://www.techsupportforum.com/alte...petitions.html

I will be posting on the Apple Discussion forums about this too.

Very frustrating.

:-(

Any feedback, ladies and gents?

Thank you

Dr Sly

[funkydata]

I did that when I received my macbook pro out of habit with dell PCs. The behaviour appeared later on.

Originally Posted by Karelia

I have one answer for both of you, and it seems to resolve most all Leopard-related quirks.

Reinstall Leopard.

[Mikejakester]

I got a Macbook 13" back in January this year - Everything was great until last week - My Control Key Got stuck on and my keyboard was useless... RPRAM Reset was unsuccessful. Right now I am using a an external USB Keyboard. I did a clean re-install of the Leopard and the problem changed from having the Control Key stuck to having the SHIFT key stuck - Another particular symptom is that the keyboard (using Keyboard viewer) will reset it self when ever I use the external keyboard, meaning, that if I hit any key in the internal keyboard the shift key will lock it self again, but as soon as I use the external keyboard again the shift will unlock. It is really weird.

[richardveenstra]

Hi,

new here on the forum.

Seems I have the same problem here since this morning.

It started with the up-arrow key, thought it was my keyboard.
After cleaning my keyboard and might mouse, problem still existed.

After that, I connected another keyboard and mouse to my Mac Pro and rebooted.
This time, it was the "+" key. I rebooted, connected the new keyboard and mouse to another USB port and now the "-" key got "stuck".

Funny is, that I have two separate HD's with different installs of Leopard.
The problem exists on BOTH installs.

What's going on here?
Any news about this?

Any help appreciated!

Best
Richard

[TaylorAudio]

"7" key on the 10-key pad for me.

I too would love an answer here. Thanks!

J.R.