qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Carlos A. M. dos Santos" <unixmania@gmail.com>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] unknown keycodes `xfree86(abnt2)_aliases(qwerty)'
Date: Sun, 12 Apr 2009 23:02:14 -0300	[thread overview]
Message-ID: <e71790db0904121902p60b7d439oce535b8cc9b5b303@mail.gmail.com> (raw)

Hello,

Each time I start qemu I see this message:

    unknown keycodes `xfree86(abnt2)_aliases(qwerty)', please report
to qemu-devel@nongnu.org

This is harmless, as far as I can tell, since the keyboard still works
correctly. I'm reporting just because qemu asks me to do it. :-)

Here is a summary of my environment:

- FreeBSD 7-STABLE, updated on March 29
- kqemu-kmod-devel-1.4.0.p1_2
- qemu-0.10.2
- xorg-server-1.5.3_7,1

My xorg.conf configures the keyboard to Brazilian Portuguese layout
(a.k.a. ABNT2):

Section "InputDevice"
        Identifier  "Keyboard0"
        Driver      "kbd"
        Option      "XkbRules"  "xorg"
        Option      "XkbModel"  "abnt2"
        Option      "XkbLayout" "br"
EndSection

The message goes away if I invoke qemu with "-k pt-br" but if in this
case I see "Warning: no scancode found for keysym 314" when  I press
an accent dead key. This is a known problem, according to what I found
searching in list archives.

I do not subscribe qemu-devel so please CC'me in your answers.

-- 
My preferred quotation of Robert Louis Stevenson is "You cannot
make an omelette without breaking eggs". Not because I like the
omelettes, but because I like the sound of eggs being broken.

             reply	other threads:[~2009-04-13  2:02 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-13  2:02 Carlos A. M. dos Santos [this message]
2009-04-13 11:37 ` [Qemu-devel] unknown keycodes `xfree86(abnt2)_aliases(qwerty)' andrzej zaborowski

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=e71790db0904121902p60b7d439oce535b8cc9b5b303@mail.gmail.com \
    --to=unixmania@gmail.com \
    --cc=qemu-devel@nongnu.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;
as well as URLs for NNTP newsgroup(s).