public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Patrick Cole <z@amused.net>
To: linux-kernel@vger.kernel.org
Subject: Touchpad / keyboard behaving strangely on 2.6
Date: Wed, 14 Jan 2004 17:11:34 +1030	[thread overview]
Message-ID: <20040114064134.GA2257@jaded> (raw)

Since moving to 2.6 (same in .0 and .1), the synaptics touchpad on 
my Dell I8100 will occasionally stop moving for a few seconds, sometimes
for as much as 5 seconds, then just come back and start working again, 
while the rest of the system is fully responsive (can switch X
workspaces, launch stuff with my keybindings, etc).

Additionally, the keyboard repeat rate seems to be malfunctioning.
Almost everytime I use one of my key bindings in sawfish (Ctrl-Alt-T) to 
open a terminal window (wterm), I get a 1 or so second delay before 
the terminal actually opens, and I always get two or three open instead
of just one, even with the repeat delay set very high and using a
very swift press.  The symptom only goes away when I turn the repeat
off completely (xset r off) or I go back to my 2.4 kernel.

Anybody have any thoughts?

Patrick

-- 
Patrick Cole <z@amused.net>

                 reply	other threads:[~2004-01-14  6:47 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20040114064134.GA2257@jaded \
    --to=z@amused.net \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox