From: beto@plan9.cs.su.oz.au beto@plan9.cs.su.oz.au
Subject: keyboard bug
Date: Tue, 2 Apr 1996 13:19:27 -0500 [thread overview]
Message-ID: <19960402181927.3DASNDVh7Z1DtbycwutJvxODxPHn8RfPUJpumfFJnuc@z> (raw)
Hi,
I've been leaving with a bug for quite a while and
I decided to share it with you.
The problem is that sometime I loose access to
the keyboard, which means that the system does not
process caracteres coming from the keyboard but it does
process already entered caracteres, as for example
when doing cut and paste. Most of the time the bug
appears after running a cpu-intensive job for a while.
Usually, before I loose the keyboard a message appears
in the screen saying 'unknown key %d'.
Has anyone else experienced this problem?
Any idea of how to fixed or where to look? I though
it could be an scheduling problem but there isn't
a process serving the keyboard, it's a KIOQ.
Any comments would be appreacited.
bye
next reply other threads:[~1996-04-02 18:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
1996-04-02 18:19 beto [this message]
-- strict thread matches above, loose matches on Subject: below --
1996-04-02 18:54 beto
1996-04-02 5:47 Lucio
1996-04-02 3:58 philw
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=19960402181927.3DASNDVh7Z1DtbycwutJvxODxPHn8RfPUJpumfFJnuc@z \
--to=beto@plan9.cs.su.oz.au \
/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;
as well as URLs for NNTP newsgroup(s).