[Qemu-devel] AltGr keystrokes

[Qemu-devel] AltGr keystrokes

[Gaetano Sferra]

Hello,
I'm using Qemu 0.8.2 on Microsoft Windows XP and the AltGr key doesn't seem 
to work at all using windib (using directx support it works but the keyboard 
mappig isn't correct, even forcing a keymap via -k option). I tried to press 
AltGr+<everything> but no output is produced. This is a real matter because 
it's impossible to print out (in a easy way) character as: @,#,[ and ],{ and 
} and €.
There are workarounds?

Thank you,
--
Gaedevel

_________________________________________________________________
Personalizza MSN Messenger con sfondi e fotografie! 
http://spaces.msn.com/morespaces.aspx

RE: [Qemu-devel] AltGr keystrokes

[Gaetano Sferra]

So nobody have ideas on how to solve the keyboard problem?
I'm looking and seeking into the user's forum, there are similar questions 
but there aren't replies...


>From: "Gaetano Sferra" <mynewsletters@hotmail.it>
>Reply-To: qemu-devel@nongnu.org
>To: qemu-devel@nongnu.org
>Subject: [Qemu-devel] AltGr keystrokes
>Date: Wed, 26 Jul 2006 13:24:57 +0200
>MIME-Version: 1.0
>X-Originating-IP: [217.59.38.133]
>X-Originating-Email: [mynewsletters@hotmail.it]
>X-Sender: mynewsletters@hotmail.it
>Received: from lists.gnu.org ([199.232.76.165]) by 
>bay0-pamc1-f6.bay0.hotmail.com with Microsoft SMTPSVC(6.0.3790.2444); Wed, 
>26 Jul 2006 04:25:51 -0700
>Received: from localhost ([127.0.0.1] helo=lists.gnu.org)by lists.gnu.org 
>with esmtp (Exim 4.43)id 1G5hWQ-00042U-WBfor mynewsletters@hotmail.it; Wed, 
>26 Jul 2006 07:25:51 -0400
>Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)id 
>1G5hVk-00041v-5Lfor qemu-devel@nongnu.org; Wed, 26 Jul 2006 07:25:08 -0400
>Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)id 
>1G5hVh-00040t-Bufor qemu-devel@nongnu.org; Wed, 26 Jul 2006 07:25:07 -0400
>Received: from [199.232.76.173] (helo=monty-python.gnu.org)by lists.gnu.org 
>with esmtp (Exim 4.43) id 1G5hVh-00040j-47for qemu-devel@nongnu.org; Wed, 
>26 Jul 2006 07:25:05 -0400
>Received: from [65.54.246.236] (helo=bay0-omc3-s36.bay0.hotmail.com)by 
>monty-python.gnu.org with esmtp (Exim 4.52) id 1G5hXD-0000FV-GLfor 
>qemu-devel@nongnu.org; Wed, 26 Jul 2006 07:26:39 -0400
>Received: from hotmail.com ([65.54.186.70]) by 
>bay0-omc3-s36.bay0.hotmail.comwith Microsoft SMTPSVC(6.0.3790.1830); Wed, 
>26 Jul 2006 04:25:01 -0700
>Received: from mail pickup service by hotmail.com with Microsoft 
>SMTPSVC;Wed, 26 Jul 2006 04:25:01 -0700
>Received: from 69.45.64.21 by by16fd.bay16.hotmail.msn.com with HTTP;Wed, 
>26 Jul 2006 11:24:57 GMT
>X-Message-Info: LsUYwwHHNt3660MmjhEvYg2f34OAemlK+3Wz9fWrJ/U=
>X-OriginalArrivalTime: 26 Jul 2006 11:25:01.0062 
>(UTC)FILETIME=[22261A60:01C6B0A6]
>X-BeenThere: qemu-devel@nongnu.org
>X-Mailman-Version: 2.1.5
>Precedence: list
>List-Id: qemu-devel.nongnu.org
>List-Unsubscribe: 
><http://lists.nongnu.org/mailman/listinfo/qemu-devel>,<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
>List-Archive: <http://lists.gnu.org/pipermail/qemu-devel>
>List-Post: <mailto:qemu-devel@nongnu.org>
>List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
>List-Subscribe: 
><http://lists.nongnu.org/mailman/listinfo/qemu-devel>,<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
>Errors-To: qemu-devel-bounces+mynewsletters=hotmail.it@nongnu.org
>Return-Path: qemu-devel-bounces+mynewsletters=hotmail.it@nongnu.org
>
>Hello,
>I'm using Qemu 0.8.2 on Microsoft Windows XP and the AltGr key doesn't seem 
>to work at all using windib (using directx support it works but the 
>keyboard mappig isn't correct, even forcing a keymap via -k option). I 
>tried to press AltGr+<everything> but no output is produced. This is a real 
>matter because it's impossible to print out (in a easy way) character as: 
>@,#,[ and ],{ and } and €.
>There are workarounds?
>
>Thank you,
>--
>Gaedevel
>
>_________________________________________________________________
>Personalizza MSN Messenger con sfondi e fotografie! 
>http://spaces.msn.com/morespaces.aspx
>
>
>
>_______________________________________________
>Qemu-devel mailing list
>Qemu-devel@nongnu.org
>http://lists.nongnu.org/mailman/listinfo/qemu-devel

_________________________________________________________________
Personalizza MSN Messenger con sfondi e fotografie! 
http://spaces.msn.com/morespaces.aspx

Re: [Qemu-devel] AltGr keystrokes

[Eric Hameleers]

Gaetano Sferra wrote:
> So nobody have ideas on how to solve the keyboard problem?
> I'm looking and seeking into the user's forum, there are similar
> questions but there aren't replies...

Hi,

I am having sort of similar problems with the keymapping. Rather than
coming up with an answer, I like to add my own remarks, maybe they are
related:

First, I want to make it clear I don't have knowledge of the keyboard
mapping process in VNC client/server communication. If I write
nonsense here, please correct me...

When I run qemu-0.8.2 with the VNC server enabled and then connecting
to my QEMU's VNC server on a PC with a dutch keyboard layout, there is
no way I can get the keyboard to function 100% correct.

Normally, when I use a vnc client to connect to any "normal" VNC
server like the one from RealVNC, it does not matter if I run the
vncclient with a dutch or a US keyboard, the keypresses are correctly
translated.

But with the QEMU's built-in VNC server (as opposed to the now-gone
RFB patch from Johannes Schindelin which worked fine for me) some keys
work, some don't give any output at all, and others print incorrect
characters. This is when I add "-k nl". Things get a little better
when I also "loadkeys nl.map" on the QEMU guest but still the result
is not at all 100% OK.

Without the "-k" option (thus reverting to the default en-us) I get
other combinations of keys that work/print incorrect chars/don't
output at all, still not 100% correct.

Are other people with international keyboards having these issues as
well? What is the difference with the old RFB patch that the currently
built-in VNC server handles differently?

Eric

-- 
Eric Hameleers

Re: [Qemu-devel] AltGr keystrokes

[Johannes Schindelin]

Hi,

On Mon, 31 Jul 2006, Eric Hameleers wrote:

> What is the difference with the old RFB patch that the currently 
> built-in VNC server handles differently?

The old RFB patch uses the infrastructure of LibVNCServer, which has been 
tried and tested.

Unfortunately, Anthony decided to fix the issue he had not by submitting a 
patch to LibVNCServer, but by completely rewriting the functionality. So, 
the old RFB patch and the built-in VNC server share only the goal.

Ciao,
Dscho

Re: [Qemu-devel] AltGr keystrokes

[Eric Hameleers]

Johannes Schindelin wrote:

> Hi,
> 
> On Mon, 31 Jul 2006, Eric Hameleers wrote:
> 
> 
>>What is the difference with the old RFB patch that the currently 
>>built-in VNC server handles differently?
> 
> 
> The old RFB patch uses the infrastructure of LibVNCServer, which has been 
> tried and tested.
> 
> Unfortunately, Anthony decided to fix the issue he had not by submitting a 
> patch to LibVNCServer, but by completely rewriting the functionality. So, 
> the old RFB patch and the built-in VNC server share only the goal.
> 
> Ciao,
> Dscho
> 

Hi Johannes

Yes I know, and although the libvncserver based patch was cumbersome
over high-latency connections it was still useful (and I was able to
access the monitor). With Anthony's re-implementation I get great
improvements regarding the screen refresh, but I have lost access to
the monitor (so I have to use a separate telnet connection now) and
most importantly, I cannot use my keyboard reliably which makes this
implementation effectively useless to me.
I guess I will have to look into the keymaps myself, but on first
quick inspection I did not find anything out of order in the "nl" keymap.

Eric

-- 
Eric Hameleers
RedHat Certified Engineer #808003505607683
Linux Knowledge Center, IBM Global Services
Email:  alien@nl.ibm.com
Jabber: alien@jabber.xs4all.nl

[Qemu-devel] Re: AltGr keystrokes

[Anthony Liguori]

On Mon, 31 Jul 2006 12:13:14 +0200, Eric Hameleers wrote:

> When I run qemu-0.8.2 with the VNC server enabled and then connecting to
> my QEMU's VNC server on a PC with a dutch keyboard layout, there is no
> way I can get the keyboard to function 100% correct.

Which keys aren't working for you?  If you could possibly annotate
vnc.c:do_key_event() to print out sym and keycode that would be even more
helpful.

Regards,

Anthony Liguori

> Normally, when I use a vnc client to connect to any "normal" VNC server
> like the one from RealVNC, it does not matter if I run the vncclient
> with a dutch or a US keyboard, the keypresses are correctly translated.
> 
> But with the QEMU's built-in VNC server (as opposed to the now-gone RFB
> patch from Johannes Schindelin which worked fine for me) some keys work,
> some don't give any output at all, and others print incorrect
> characters. This is when I add "-k nl". Things get a little better when
> I also "loadkeys nl.map" on the QEMU guest but still the result is not
> at all 100% OK.
> 
> Without the "-k" option (thus reverting to the default en-us) I get
> other combinations of keys that work/print incorrect chars/don't output
> at all, still not 100% correct.
> 
> Are other people with international keyboards having these issues as
> well? What is the difference with the old RFB patch that the currently
> built-in VNC server handles differently?
> 
> Eric

[Qemu-devel] Re: AltGr keystrokes

[Anthony Liguori]

On Mon, 31 Jul 2006 12:13:14 +0200, Eric Hameleers wrote:

> Are other people with international keyboards having these issues as well?
> What is the difference with the old RFB patch that the currently built-in
> VNC server handles differently?

The old VNC patch uses LibVNCServer which is a derivative of the old Xvnc
codebase.  Details of why libvncserver didn't meet my goals have been
addressed in previous threads but suffice to say, I felt that starting
from scratch was necessary.

The VNC protocol does a rather poor job in defining what keycodes
correspond to what key events.  It roughly says to follow the X keysyms
but warns that many clients do weird things and does not actually document
all of those things.

Additionally, there's also translation to QEMU's keycodes.  Fortunately,
these things are easy to fix once we know what codes are being sent by the
client.  Unfortunately, I don't have an nl keyboard lying around so I need
some help figuring that out :-)

Regards,

Anthony Liguori

> Eric

RE: [Qemu-devel] Re: AltGr keystrokes

[Gaetano Sferra]

Wait!
This doesn't reply to my question, I never talked about VNC servers or 
clients.
If you want replies about a similar but quite different matter, post a new 
topic, don't "takeover" the mine.

Thank you,
--
Gaetano Sferra

_________________________________________________________________
Personalizza MSN Messenger con sfondi e fotografie! 
http://spaces.msn.com/morespaces.aspx

[Qemu-devel] Re: AltGr keystrokes

[Edu]

Hi,

I also have issues with extended characters in my keyboard layout when
using VNC. Part of them seem to be caused by sign extension in
function read_u32 from vnc.c, which should not be done.

I need to do some more testing, though.

Eduardo Felipe

[Qemu-devel] Re: AltGr keystrokes

[Anthony Liguori]

On Wed, 02 Aug 2006 02:22:44 +0200, Edu wrote:

> Hi,
> 
> I also have issues with extended characters in my keyboard layout when
> using VNC. Part of them seem to be caused by sign extension in function
> read_u32 from vnc.c, which should not be done.

You're right, I'll submit a patch to fix that.  Let me know if it helps.

Regards,

Anthony Liguori
 
> I need to do some more testing, though.
>
> Eduardo Felipe

Re: [Qemu-devel] Re: AltGr keystrokes

[Edu]

2006/8/2, Anthony Liguori <anthony@codemonkey.ws>:
>
> You're right, I'll submit a patch to fix that.  Let me know if it helps.
>

Well, it indeed helps to some extent, but it's not enough.

Tracking down the problem I've found out that modifiers after
scancodes in keymap files are completely ignored in function
parse_keyboard_layout (keymaps.c).

In "es" keymap we find:

quotedbl 0x03 shift
at 0x03 altgr

Which means
" ==> Shift + 2
@ ==> AltGr + 2

Logging TightVNC client messages:

[ PRESS SHIFT ]
  VNC msg: DOWN 0xFFE1 --> OS receives keycode: 0x2A

[ PRESS 2 ]
  VNC msg: DOWN 0x22   --> OS receives keycode: 0x03

[ RELEASE 2 ]
  VNC msg: UP   0x22   --> OS receives keycode: 0x03

[ RELEASE SHIFT ]
  VNC msg: UP   0xFFE1 --> OS receives keycode: 0x2A

This works correctly and double quote is printed, but...

[ PRESS ALTGR ]
  VNC msg: DOWN 0xFFE3 --> OS receives keycode: 0x1D
  VNC msg: DOWN 0xFFEA --> OS receives keycode: 0x38

[ PRESS 2 ]
  VNC msg: UP   0xFFE3 --> OS receives keycode: 0x1D
  VNC msg: UP   0xFFEA --> OS receives keycode: 0x38
  VNC msg: DOWN 0x40   --> OS receives keycode: 0x03
  VNC msg: DOWN 0xFFEA --> OS receives keycode: 0x38
  VNC msg: UP   0xFFE3 --> OS receives keycode: 0x1D
  VNC msg: UP   0xFFE3 --> OS receives keycode: 0x1D
  VNC msg: UP   0xFFEA --> OS receives keycode: 0x38
  VNC msg: UP   0x40   --> OS receives keycode: 0x03
  VNC msg: DOWN 0xFFEA --> OS receives keycode: 0x38
  VNC msg: UP   0xFFE3 --> OS receives keycode: 0x1D
  VNC msg: UP   0xFFE3 --> OS receives keycode: 0x1D
  VNC msg: UP   0xFFEA --> OS receives keycode: 0x38

... doesn't work at all.

As you can see, VNC client sends messages to release AltGr modifier
before sending 0x40 symbol ( @ ). It relies on the server to know how
to get it. As the OS receives a bare 0x03 keycode, the resulting
character is 2. Qemu should send to the OS the AltGr keydown event
before the 0x03 scancode, as the keymap says. Double quote case
shouldn't be affected by the extra Shift keydown event.

Regards,
Eduardo Felipe