From: Gerd Hoffmann <kraxel@redhat.com>
To: Michael Tokarev <mjt@tls.msk.ru>
Cc: "R. Lemos" <rslemos@gmail.com>,
772422@bugs.debian.org, qemu-devel <qemu-devel@nongnu.org>,
Joao Luis Meloni Assirati <jlma@nonada.if.usp.br>
Subject: Re: [Qemu-devel] ABNT2 keys again
Date: Fri, 22 May 2015 15:20:09 +0200 [thread overview]
Message-ID: <1432300809.12533.55.camel@nilsson.home.kraxel.org> (raw)
In-Reply-To: <555F2AC7.80807@msgid.tls.msk.ru>
Hi,
> > Anyone having such a keyboard and willing to run some tests?
>
> Adding Cc's. This has been reported to debian too,
> http://bugs.debian.org/772422 (also in Cc).
Ok, so just replying should stick this into the debian bug tracker,
right?
Ok, instructions are here:
(a) Go grab https://www.kraxel.org/cgit/input/ please (could be there
even is a debian package for this stuff).
(b) Use 'lsinput' to figure which input device is your keyboard (on
the host machine).
(c) Then use 'input-events <device-number>' to get a input event log
printed to the terminal. Type each missing key once.
(d) Send me the log (with annotation which key is which).
thanks,
Gerd
next prev parent reply other threads:[~2015-05-22 13:21 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-30 5:01 [Qemu-devel] ABNT2 keys again Michael Tokarev
2015-05-20 11:44 ` Michael Tokarev
2015-05-22 10:01 ` Gerd Hoffmann
2015-05-22 13:10 ` Michael Tokarev
2015-05-22 13:20 ` Gerd Hoffmann [this message]
2015-05-22 13:39 ` Michael Tokarev
2015-05-22 16:10 ` Joao Luis Meloni Assirati
2015-05-26 7:58 ` Gerd Hoffmann
2015-05-26 20:51 ` Joao Luis Meloni Assirati
2015-05-27 14:11 ` Gerd Hoffmann
2015-05-26 14:01 ` Gerd Hoffmann
2015-05-26 15:52 ` R. Lemos
2015-05-26 21:24 ` Joao Luis Meloni Assirati
2015-05-27 14:18 ` Gerd Hoffmann
2015-05-22 15:03 ` Joao Luis Meloni Assirati
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=1432300809.12533.55.camel@nilsson.home.kraxel.org \
--to=kraxel@redhat.com \
--cc=772422@bugs.debian.org \
--cc=jlma@nonada.if.usp.br \
--cc=mjt@tls.msk.ru \
--cc=qemu-devel@nongnu.org \
--cc=rslemos@gmail.com \
/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).