From owner-freebsd-current@FreeBSD.ORG Mon Dec 24 08:15:17 2007 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C976116A417 for ; Mon, 24 Dec 2007 08:15:17 +0000 (UTC) (envelope-from silby@silby.com) Received: from relay03.pair.com (relay03.pair.com [209.68.5.17]) by mx1.freebsd.org (Postfix) with SMTP id 66E0F13C4D5 for ; Mon, 24 Dec 2007 08:15:17 +0000 (UTC) (envelope-from silby@silby.com) Received: (qmail 36040 invoked from network); 24 Dec 2007 08:15:16 -0000 Received: from unknown (HELO localhost) (unknown) by unknown with SMTP; 24 Dec 2007 08:15:16 -0000 X-pair-Authenticated: 209.68.2.70 Date: Mon, 24 Dec 2007 02:15:17 -0600 (CST) From: Mike Silbersack To: current@freebsd.org Message-ID: <20071224020713.F1390@odysseus.silby.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: Subject: Repeated or missed keys after upgrading from 6.2 to 7.0 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 24 Dec 2007 08:15:17 -0000 In order to eat my own dog food, I upgraded my laptop from 6.2 to 7.0. This seemed to have gone well, until I started writing a long e-mail while sitting on the couch today. As I was typing the e-mail, I noticed that my typing skills seemed to have gone missing; there were words missing 2-3 letters, and other places where I was apparently holding down keyyyys. Heh, that's a real example of the phenomenon right there. After a while I realized that I was not typing sloppily, but that in fact keys are being lost in certain cases and duplicated in others. Since I did not rebuild any ports or packages, I'm convinced that this is directly related to the 7.0 upgrade. This behavior has shown up when running a local copy of pine (inside konsole), chatting in ksirc, and in a few other programs. (I'm running KDE.) I think it happens more when on battery than when plugged into an outlet. I'm running xbattbar, so it could be querying the battery status and causing problems. This is using the laptop's built-in keyboard (non-USB.) I'm going to try to track this down, although I don't know how successful I'll be. I'd like to know if anyone else has seen this problem and if they have any additional information that might help me track it down faster. Thanks, Mike "Silby" Silbersack