<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	>
<channel>
	<title>Comments on: OSX Leopard: Keyboard Problems</title>
	<atom:link href="http://fredericiana.com/2007/11/27/osx-leopard-keyboard-problems/feed/" rel="self" type="application/rss+xml" />
	<link>http://fredericiana.com/2007/11/27/osx-leopard-keyboard-problems/</link>
	<description>Open Source, The Web, And German-American Oddities</description>
	<pubDate>Fri, 21 Nov 2008 22:25:36 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.3</generator>
		<item>
		<title>By: Denise Anne</title>
		<link>http://fredericiana.com/2007/11/27/osx-leopard-keyboard-problems/#comment-159394</link>
		<dc:creator>Denise Anne</dc:creator>
		<pubDate>Tue, 10 Jun 2008 03:14:49 +0000</pubDate>
		<guid isPermaLink="false">http://fredericiana.com/2007/11/27/osx-leopard-keyboard-problems/#comment-159394</guid>
		<description>After I installed the new leopard my keyboard went backwards. I have to have the numlock and cap lock on in order for my keyboard to work this is crazy. Has anyone else had this problem?</description>
		<content:encoded><![CDATA[<p>After I installed the new leopard my keyboard went backwards. I have to have the numlock and cap lock on in order for my keyboard to work this is crazy. Has anyone else had this problem?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Matthew Pare</title>
		<link>http://fredericiana.com/2007/11/27/osx-leopard-keyboard-problems/#comment-156410</link>
		<dc:creator>Matthew Pare</dc:creator>
		<pubDate>Thu, 29 May 2008 16:29:18 +0000</pubDate>
		<guid isPermaLink="false">http://fredericiana.com/2007/11/27/osx-leopard-keyboard-problems/#comment-156410</guid>
		<description>I'm running Dual 2 GHz PPC G5, 2.5 GB DDR2 SDRAM, OS X 10.5.3 and I'm experiencing keyboard problems. I experienced the problem with 10.5.1, 10.5.2 and still with 10.5.3. Like most others the problem seems to happen when waking the computer from a nap. It seems that 1/3 of the time all is fine, another 1/3 of the time the mouse becomes unresponsive, and the remaining 1/3 of the time its just the keyboard that is unresponsive. I've encountered all three situations repeatably now. I use a Macally iKey keyboard as I don't care for the apple keyboards and a mighty mouse plugged into one of the 2 usb ports on the macally iKey. I am able to resolve unresponsive keyboard and unresponsive mouse by disconnecting the keyboard from the computer and plugging it back in. Once, when the keyboard became unresponsive my computer had the bluetooth lost connection wizard open. Could these issues arrise from some sort of blue tooth misconfiguration or is this apple's way of recognizing there is a problem and trying to auto solution it. Seems like a poor move if there never has been a blue tooth keyboard or mouse paired with the system. It seems that most people encountering this issue are running notebooks so maybe these details will help. On to look for an alternative solution.

Cheers,
-Mpare</description>
		<content:encoded><![CDATA[<p>I&#8217;m running Dual 2 GHz PPC G5, 2.5 GB DDR2 SDRAM, OS X 10.5.3 and I&#8217;m experiencing keyboard problems. I experienced the problem with 10.5.1, 10.5.2 and still with 10.5.3. Like most others the problem seems to happen when waking the computer from a nap. It seems that 1/3 of the time all is fine, another 1/3 of the time the mouse becomes unresponsive, and the remaining 1/3 of the time its just the keyboard that is unresponsive. I&#8217;ve encountered all three situations repeatably now. I use a Macally iKey keyboard as I don&#8217;t care for the apple keyboards and a mighty mouse plugged into one of the 2 usb ports on the macally iKey. I am able to resolve unresponsive keyboard and unresponsive mouse by disconnecting the keyboard from the computer and plugging it back in. Once, when the keyboard became unresponsive my computer had the bluetooth lost connection wizard open. Could these issues arrise from some sort of blue tooth misconfiguration or is this apple&#8217;s way of recognizing there is a problem and trying to auto solution it. Seems like a poor move if there never has been a blue tooth keyboard or mouse paired with the system. It seems that most people encountering this issue are running notebooks so maybe these details will help. On to look for an alternative solution.</p>
<p>Cheers,<br />
-Mpare</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: fernando paulsen</title>
		<link>http://fredericiana.com/2007/11/27/osx-leopard-keyboard-problems/#comment-121991</link>
		<dc:creator>fernando paulsen</dc:creator>
		<pubDate>Mon, 10 Mar 2008 22:10:52 +0000</pubDate>
		<guid isPermaLink="false">http://fredericiana.com/2007/11/27/osx-leopard-keyboard-problems/#comment-121991</guid>
		<description>Allen, did the keyboard patch work? I have done everything, updating to 10.5.2, just put the new Keyboard update with recent firmware, and still have the intermittent keyboard non response.</description>
		<content:encoded><![CDATA[<p>Allen, did the keyboard patch work? I have done everything, updating to 10.5.2, just put the new Keyboard update with recent firmware, and still have the intermittent keyboard non response.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: allan egleston</title>
		<link>http://fredericiana.com/2007/11/27/osx-leopard-keyboard-problems/#comment-121609</link>
		<dc:creator>allan egleston</dc:creator>
		<pubDate>Sat, 08 Mar 2008 23:22:06 +0000</pubDate>
		<guid isPermaLink="false">http://fredericiana.com/2007/11/27/osx-leopard-keyboard-problems/#comment-121609</guid>
		<description>M macbook pro keyboard just went dead this last week Am using a ps 2 ( p.c) keyboard to type at u. Apple care failed to correct the problem, and  a local (Sonora , Ca ) area tech said that this is not uncommon for apple since the last run of tiger to lepoard 10.5.2. Update... Just got the keypoard update patch and installed this patch. I am glad that Im not the only one who has this problem. Allan Egleston. Sonora, Ca.</description>
		<content:encoded><![CDATA[<p>M macbook pro keyboard just went dead this last week Am using a ps 2 ( p.c) keyboard to type at u. Apple care failed to correct the problem, and  a local (Sonora , Ca ) area tech said that this is not uncommon for apple since the last run of tiger to lepoard 10.5.2. Update&#8230; Just got the keypoard update patch and installed this patch. I am glad that Im not the only one who has this problem. Allan Egleston. Sonora, Ca.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: fredericiana &#187; Blog Archive &#187; Apple (Allegedly) Fixes Leopard Keyboard Bug</title>
		<link>http://fredericiana.com/2007/11/27/osx-leopard-keyboard-problems/#comment-103431</link>
		<dc:creator>fredericiana &#187; Blog Archive &#187; Apple (Allegedly) Fixes Leopard Keyboard Bug</dc:creator>
		<pubDate>Wed, 19 Dec 2007 10:57:36 +0000</pubDate>
		<guid isPermaLink="false">http://fredericiana.com/2007/11/27/osx-leopard-keyboard-problems/#comment-103431</guid>
		<description>[...] Apple released a system update that is supposed to fix the severe &#8220;keyboard unresponsive&#8221; bug in OS&#160;X [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] Apple released a system update that is supposed to fix the severe &#8220;keyboard unresponsive&#8221; bug in OS&nbsp;X [&#8230;]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Fred</title>
		<link>http://fredericiana.com/2007/11/27/osx-leopard-keyboard-problems/#comment-103416</link>
		<dc:creator>Fred</dc:creator>
		<pubDate>Wed, 19 Dec 2007 08:41:40 +0000</pubDate>
		<guid isPermaLink="false">http://fredericiana.com/2007/11/27/osx-leopard-keyboard-problems/#comment-103416</guid>
		<description>Thanks for the info, man! After my next class, I'll install it and will make sure to get a followup-post on my blog. Thanks to all the other people who told me about the patch, too!</description>
		<content:encoded><![CDATA[<p>Thanks for the info, man! After my next class, I&#8217;ll install it and will make sure to get a followup-post on my blog. Thanks to all the other people who told me about the patch, too!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Marc Tanenbaum</title>
		<link>http://fredericiana.com/2007/11/27/osx-leopard-keyboard-problems/#comment-103412</link>
		<dc:creator>Marc Tanenbaum</dc:creator>
		<pubDate>Wed, 19 Dec 2007 06:37:37 +0000</pubDate>
		<guid isPermaLink="false">http://fredericiana.com/2007/11/27/osx-leopard-keyboard-problems/#comment-103412</guid>
		<description>Apple issued a patch for this problem yesterday (17 December, 2007). Updating system software should resolve the issue (fingers crossed!)</description>
		<content:encoded><![CDATA[<p>Apple issued a patch for this problem yesterday (17 December, 2007). Updating system software should resolve the issue (fingers crossed!)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Deconverted</title>
		<link>http://fredericiana.com/2007/11/27/osx-leopard-keyboard-problems/#comment-103355</link>
		<dc:creator>Deconverted</dc:creator>
		<pubDate>Tue, 18 Dec 2007 22:54:50 +0000</pubDate>
		<guid isPermaLink="false">http://fredericiana.com/2007/11/27/osx-leopard-keyboard-problems/#comment-103355</guid>
		<description>I have recently seen some fanboys suggesting that mb/mbp users carry along a usb mouse and keyboard in order to solve this problem (thus epitomizing the very essence of portability :-).  This situation is getting more and more hilarious by the day!  However, I truly feel bad for those who are putting up with this problem while awaiting a fix from the apple overlords.  I am really glad that I took my macbook back last month (it's ASUS F8 replacement has been flawless).  I can't imagine having put up with it for this long.  Might I suggest dual booting Ubuntu until this entire mess is resolved?  Good luck to you all!</description>
		<content:encoded><![CDATA[<p>I have recently seen some fanboys suggesting that mb/mbp users carry along a usb mouse and keyboard in order to solve this problem (thus epitomizing the very essence of portability :-).  This situation is getting more and more hilarious by the day!  However, I truly feel bad for those who are putting up with this problem while awaiting a fix from the apple overlords.  I am really glad that I took my macbook back last month (it&#8217;s ASUS F8 replacement has been flawless).  I can&#8217;t imagine having put up with it for this long.  Might I suggest dual booting Ubuntu until this entire mess is resolved?  Good luck to you all!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Fred</title>
		<link>http://fredericiana.com/2007/11/27/osx-leopard-keyboard-problems/#comment-103305</link>
		<dc:creator>Fred</dc:creator>
		<pubDate>Tue, 18 Dec 2007 18:00:42 +0000</pubDate>
		<guid isPermaLink="false">http://fredericiana.com/2007/11/27/osx-leopard-keyboard-problems/#comment-103305</guid>
		<description>Holding Shift or any other key won't really help the situation much, other than you noticing when it happens to work again. After a short period of time however, the keyboard will just stop working again.</description>
		<content:encoded><![CDATA[<p>Holding Shift or any other key won&#8217;t really help the situation much, other than you noticing when it happens to work again. After a short period of time however, the keyboard will just stop working again.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tom</title>
		<link>http://fredericiana.com/2007/11/27/osx-leopard-keyboard-problems/#comment-103268</link>
		<dc:creator>Tom</dc:creator>
		<pubDate>Tue, 18 Dec 2007 14:44:50 +0000</pubDate>
		<guid isPermaLink="false">http://fredericiana.com/2007/11/27/osx-leopard-keyboard-problems/#comment-103268</guid>
		<description>I am having this keyboard problem - Core Duo MacBook - so far I've found that going back into Sleep through the menu and bringing out again seems to fix it some of the time, but I will try holding Shift next time.</description>
		<content:encoded><![CDATA[<p>I am having this keyboard problem &#8211; Core Duo MacBook &#8211; so far I&#8217;ve found that going back into Sleep through the menu and bringing out again seems to fix it some of the time, but I will try holding Shift next time.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
