From: Philipp Hahn <hahn@univention.de>
To: qemu-devel@nongnu.org
Cc: Fabian Holler <fabian.holler@profitbricks.com>
Subject: Re: [Qemu-devel] Keysymbol interpretation missing in QEMU's VNC server?
Date: Thu, 8 Mar 2012 21:24:13 +0100 [thread overview]
Message-ID: <201203082124.14187.hahn@univention.de> (raw)
In-Reply-To: <20120307105357.GA30632@fholler.de>
[-- Attachment #1: Type: text/plain, Size: 929 bytes --]
Hello Fabian,
On Wednesday 07 March 2012 11:53:57 Fabian Holler wrote:
> I'm not sure if I found a bug in QEMU's VNC keyboard layout mapping or
> if it's a general problem in the implemented VNC server:
Daniel P. Berrangé has written some very good blog entries about the VNC
problem:
<http://berrange.com/posts/2010/07/04/more-than-you-or-i-ever-wanted-to-know-about-virtual-keyboard-handling/>
They're quiet technical, but after reading them I at least concluded that VNC
is normally just broken.
I recommend using virt-viewer, with which I have mostly no such problems.
Sincerely
Philipp
--
Philipp Hahn Open Source Software Engineer hahn@univention.de
Univention GmbH Linux for Your Business fon: +49 421 22 232- 0
Mary-Somerville-Str.1 D-28359 Bremen fax: +49 421 22 232-99
http://www.univention.de/
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 197 bytes --]
next prev parent reply other threads:[~2012-03-08 20:24 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-07 10:53 [Qemu-devel] Keysymbol interpretation missing in QEMU's VNC server? Fabian Holler
2012-03-08 20:24 ` Philipp Hahn [this message]
2012-03-08 21:23 ` Fabian Holler
2012-03-08 21:30 ` Anthony Liguori
2012-03-08 22:01 ` Fabian Holler
2012-05-23 8:16 ` Erik Rull
2012-05-23 8:45 ` Erik Rull
-- strict thread matches above, loose matches on Subject: below --
2012-03-07 12:22 Fabian Holler
2014-01-14 8:45 Gonglei (Arei)
2014-01-25 5:13 Gonglei (Arei)
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=201203082124.14187.hahn@univention.de \
--to=hahn@univention.de \
--cc=fabian.holler@profitbricks.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.