From mboxrd@z Thu Jan 1 00:00:00 1970
Received: from pigeon.gentoo.org ([208.92.234.80] helo=lists.gentoo.org)
by finch.gentoo.org with esmtp (Exim 4.60)
(envelope-from <gentoo-user+bounces-96878-garchives=archives.gentoo.org@lists.gentoo.org>)
id 1MGiyA-0004s4-B1
for garchives@archives.gentoo.org; Wed, 17 Jun 2009 00:25:38 +0000
Received: from pigeon.gentoo.org (localhost [127.0.0.1])
by pigeon.gentoo.org (Postfix) with SMTP id A1D0AE0207;
Wed, 17 Jun 2009 00:25:36 +0000 (UTC)
Received: from mail-yx0-f188.google.com (mail-yx0-f188.google.com [209.85.210.188])
by pigeon.gentoo.org (Postfix) with ESMTP id 855A6E0207
for <gentoo-user@lists.gentoo.org>; Wed, 17 Jun 2009 00:25:36 +0000 (UTC)
Received: by yxe26 with SMTP id 26so479930yxe.32
for <gentoo-user@lists.gentoo.org>; Tue, 16 Jun 2009 17:25:36 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=gmail.com; s=gamma;
h=domainkey-signature:mime-version:sender:received:in-reply-to
:references:date:x-google-sender-auth:message-id:subject:from:to
:content-type:content-transfer-encoding;
bh=9WMBFE1eMjkOL0xAIKq+J+7cYTAcXCU+8LkBhPW3zg8=;
b=dOqSVSb+XUzH5GjQePsIHmI74L74ZXPRLbgmATO+NUWeFlLNb7blLGm9xLANMG9KUT
lGhOGOt11XFx8zqaTYXf5k5fLcx+peD4RMB1Q9akWUTL27191Xr37LvZOaplykOOUCoI
NPgaZsZw/jIcH0+BB4TY2O2jwGHqaMadHJ50U=
DomainKey-Signature: a=rsa-sha1; c=nofws;
d=gmail.com; s=gamma;
h=mime-version:sender:in-reply-to:references:date
:x-google-sender-auth:message-id:subject:from:to:content-type
:content-transfer-encoding;
b=rEHqXTJgPTztlEjRhkCM8NRTAaXRALRCfaUPwlEE+hNUHHj3EHUdTCgncL1RIrXxvK
xslvTNejwf1bBCvS2Az9WQjv+aEp/m9cbQ0KtjGXbFTp5iYlWHCVnzmEgBgYrHStTsOz
YIMn+X1czXm242XqPGqI0TocMi2VUPI7/a9jM=
Precedence: bulk
List-Post: <mailto:gentoo-user@lists.gentoo.org>
List-Help: <mailto:gentoo-user+help@lists.gentoo.org>
List-Unsubscribe: <mailto:gentoo-user+unsubscribe@lists.gentoo.org>
List-Subscribe: <mailto:gentoo-user+subscribe@lists.gentoo.org>
List-Id: Gentoo Linux mail <gentoo-user.gentoo.org>
X-BeenThere: gentoo-user@lists.gentoo.org
Reply-to: gentoo-user@lists.gentoo.org
MIME-Version: 1.0
Sender: paul.hartman@gmail.com
Received: by 10.151.72.1 with SMTP id z1mr16820450ybk.15.1245198331238; Tue,
16 Jun 2009 17:25:31 -0700 (PDT)
In-Reply-To: <58965d8a0906122026l62f29aeer4131ad3e0d2c9898@mail.gmail.com>
References: <58965d8a0906122026l62f29aeer4131ad3e0d2c9898@mail.gmail.com>
Date: Tue, 16 Jun 2009 19:25:31 -0500
X-Google-Sender-Auth: 4064677e7956b63e
Message-ID: <58965d8a0906161725h24645d7ble3d1b2a2e393ff43@mail.gmail.com>
Subject: [gentoo-user] Re: Keyboard handling weird... in 2.6.30?
From: Paul Hartman <paul.hartman+gentoo@gmail.com>
To: gentoo-user@lists.gentoo.org
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-Archives-Salt: 32ec45e8-0118-4da6-9479-9018038d4ec8
X-Archives-Hash: b678dc542565d493d90d76a6b40fa429
On Fri, Jun 12, 2009 at 10:26 PM, Paul
Hartman<paul.hartman+gentoo@gmail.com> wrote:
> I don't know if it is from kernel 2.6.30 or if something else changed,
> but my keyboard does not behave as normal. It seems like the "key up"
> signal from the previous key is causing the repeat of the current key
> to get interrupted. This happens everywhere, not only in X, but in
> console as well.
>
> For example, try this: Type some text, like
> XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX and then hold left arrow. Your
> cursor will move to the left until you release the key. Now try to
> hold the right arrow after you've already been holding the left arrow.
> It will start to move to the right. Previously, it would continue
> moving to the right after you released the left arrow. Now, the
> keyboard repeat STOPS once you release the PREVIOUS key. So, in other
> words, the repeating of the right arrow is stopped when I release the
> left arrow... which causes the cursor to stop, and causes me to become
> aggravated. :P
>
> Has anyone else noticed this? I hope it's not a new "feature" :) Maybe
> later tonight I'll try to go back to 2.6.29 and see if this truly was
> the thing that brought on this change.
>
Today's xorg update (and subsequent rebuilding of x11-driver/*) has
fixed the problem. So it looks like it wasn't kernel-related at all,
but a result of some xorg update in the 2 months since my previous
reboot. :)