public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Matias Grana <matiasg@dm.uba.ar>
To: gentoo user Mailing List <gentoo-user@lists.gentoo.org>
Subject: [gentoo-user] OT: loooong delay with keyboard
Date: Thu, 20 Apr 2006 15:50:47 -0300	[thread overview]
Message-ID: <20060420185047.GK1377@dm.uba.ar> (raw)

hi;
a mate at work is using KDE (actually, he has Slackware, not Gentoo,
but I guess it's the same). All of a sudden, a strange thing happened:
When he logs in his account, the keyboard has a really long delay (about
half a second) to echo each pressed key. So to write, say, 'no', he has
to press the 'n', hold it for 1/2 second, then the 'o', hold it for 1/2
second, and that's it.
This happens in only one account, the others are unaffected.

Does someone here know what the problem might be?

TIA,
Matias
-- 
gentoo-user@gentoo.org mailing list



             reply	other threads:[~2006-04-20 18:56 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-04-20 18:50 Matias Grana [this message]
2006-04-20 19:11 ` [gentoo-user] Re: OT: loooong delay with keyboard Francesco Talamona
2006-04-22 18:06   ` Matias Grana
2006-04-20 19:16 ` [gentoo-user] " Benno Schulenberg
2006-04-20 19:21 ` Mantas Povilaitis

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=20060420185047.GK1377@dm.uba.ar \
    --to=matiasg@dm.uba.ar \
    --cc=gentoo-user@lists.gentoo.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