From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) by finch.gentoo.org (Postfix) with ESMTP id 4E2871381F3 for ; Wed, 14 Nov 2012 21:03:30 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id D4C1321C045 for ; Wed, 14 Nov 2012 21:03:29 +0000 (UTC) Received: from mail-ob0-f181.google.com (mail-ob0-f181.google.com [209.85.214.181]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id 02B41E0684 for ; Wed, 14 Nov 2012 19:32:11 +0000 (UTC) Received: by mail-ob0-f181.google.com with SMTP id ta14so823341obb.40 for ; Wed, 14 Nov 2012 11:32:11 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :content-type; bh=MF1o2Y1Ar841Fe2drTJ9HEe/Dg3oB5HJULDJOgTW14I=; b=RrKIPz8VKlURa59SEJmp+WIGv8FR+4CVUUTuLebR1NxsfgXA3U7TvOoGTA2pgQcbBJ Wl3pgXY+oq10ceL+KsmFb8C3X4m3ZBppJ8lVEgZGP2BglDK6I5vpuIg5VN9LdjQhEb/J kCGrqb1mZDhjHe1wcFd5Q0jIeQORoQbM/a5vZLvSjMtFOOR5wrAQkTkFA15W6F32/a9F Nhrhzf/fECTBMlz59hUpMMTQqiXKV5cuFWkFmm5QTbt01hfXhCOyfLw+dXzPAiJa11o/ h2jw6SVuMiO1WUYKURpMaBhWj3FhpIYibZsjHVcaPLcK21AQeUTMEuZjSzrRPR2u/oSV ZUqQ== Received: by 10.60.8.35 with SMTP id o3mr9243352oea.2.1352921531196; Wed, 14 Nov 2012 11:32:11 -0800 (PST) Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-amd64@lists.gentoo.org Reply-to: gentoo-amd64@lists.gentoo.org MIME-Version: 1.0 Received: by 10.76.83.226 with HTTP; Wed, 14 Nov 2012 11:31:50 -0800 (PST) In-Reply-To: <20121114141846.65bc43bca2d2ff1f177f4c98@comcast.net> References: <20121114141846.65bc43bca2d2ff1f177f4c98@comcast.net> From: Luis Gustavo Vilela de Oliveira Date: Wed, 14 Nov 2012 17:31:50 -0200 Message-ID: Subject: Re: [gentoo-amd64] Keyboard Stops Working Under X To: gentoo-amd64@lists.gentoo.org Content-Type: multipart/alternative; boundary=e89a8fb1f79a46a69604ce79970e X-Archives-Salt: a9098f53-8aff-4176-a181-7f94c1997ad3 X-Archives-Hash: 65e0fbad67a5f67a11d91df2665a7b7d --e89a8fb1f79a46a69604ce79970e Content-Type: text/plain; charset=ISO-8859-1 What input drivers you're using? 2012/11/14 Frank Peters > Hello, > > Lately I have been experiencing a strange problem. Under X my USB keyboard > will suddenly stop working. If I press some keys they will not appear in > an > X console or in any other application. There is no warning. It just > will sporadically stop working. Usually, if I wait for several minutes > the keys will start working again. > > Fortunately, the USB mouse will continue to function normally during these > episodes. If I then immediately shutdown X using some mouse clicks, I will > again have a working keyboard. Also, the last few keys I had pressed > before > shutting down X will appear in my console. This would mean that the key > presses are detected and placed into the buffer but somehow the X > applications > do not receive them. > > I cannot pinpoint the start of this behavior to any specific system > changes, > but I suspect that the latest nvidia-drivers may be the source of the > problem. > The problem seems to coincide with one of the several nvidia updates, but > this is still a guess. > > My system is updated daily and I use only the Fvwm window manager (no > Gnome or K). > > How can I debug this further? Both the kernel log and the X log show > nothing > whatever. > > Frank Peters > > > --e89a8fb1f79a46a69604ce79970e Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable What input drivers you're using?


2012/11/14 Frank Peters <frank.peters@comcas= t.net>
Hello,

Lately I have been experiencing a strange problem. =A0Under X my USB keyboa= rd
will suddenly stop working. =A0If I press some keys they will not appear in= an
X console or in any other application. =A0There is no warning. =A0It just will sporadically stop working. =A0Usually, if I wait for several minutes the keys will start working again.

Fortunately, the USB mouse will continue to function normally during these<= br> episodes. =A0If I then immediately shutdown X using some mouse clicks, I wi= ll
again have a working keyboard. =A0Also, the last few keys I had pressed bef= ore
shutting down X will appear in my console. =A0This would mean that the key<= br> presses are detected and placed into the buffer but somehow the X applicati= ons
do not receive them.

I cannot pinpoint the start of this behavior to any specific system changes= ,
but I suspect that the latest nvidia-drivers may be the source of the probl= em.
The problem seems to coincide with one of the several nvidia updates, but this is still a guess.

My system is updated daily and I use only the Fvwm window manager (no Gnome= or K).

How can I debug this further? =A0Both the kernel log and the X log show not= hing
whatever.

Frank Peters



--e89a8fb1f79a46a69604ce79970e--