From: Lei Li <lilei@linux.vnet.ibm.com>
To: Nikola Ciprich <nikola.ciprich@linuxbox.cz>
Cc: Marian Krucina <marian.krucina@linuxbox.cz>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] weird behaviour of numlock key
Date: Fri, 12 Apr 2013 17:39:51 +0800 [thread overview]
Message-ID: <5167D667.8020409@linux.vnet.ibm.com> (raw)
In-Reply-To: <20130412084544.GF28496@pcnci.linuxbox.cz>
On 04/12/2013 04:45 PM, Nikola Ciprich wrote:
> Hi guys,
>
> I'm trying to figure out the reason of strange problem we're having.
> When I start some VM under qemu-kvm, and connect using VNC, numlock
> behaves in a funny way. First press of the numeric keyboard behaves
> like numlock is enabled (or disabled), another presses then behave
> the opposite way - therefore for example pressing '1' on numpad issues:
> <End>
> 1
> 1
>
> etc. Trying to google this up, it seems that people are having various trouble
> with numlock/capslock (usually it's disabled on remote machine while enabled locally
> or vice versa), I understand that some of them are caused by the VNC itself..
>
> However I was not able to find any mention about this particular problem
> (or solution) and I think it could be directly qemu-related..
>
> Any idea on how to debug this?
>
> I'm using qemu-1.4.0 x86_64 on RHEL6 based system.
>
> Thanks a lot for any replies in advance
Hi Nikola,
I am working on this problem. And the proposal already send
as the refference link below, you might want to take a look.
https://bugzilla.linux.ibm.com/show_bug.cgi?id=90304
If you have any suggestion, it'd be very thankful.
Thanks.
>
> BR
>
> nik
>
>
--
Lei
next prev parent reply other threads:[~2013-04-12 9:40 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-12 8:45 [Qemu-devel] weird behaviour of numlock key Nikola Ciprich
2013-04-12 9:39 ` Lei Li [this message]
2013-04-12 10:29 ` Nikola Ciprich
2013-04-15 2:11 ` Lei Li
2013-04-15 13:40 ` Gerd Hoffmann
2013-04-15 15:43 ` Nikola Ciprich
2013-04-16 6:34 ` Gerd Hoffmann
2013-04-16 6:40 ` Nikola Ciprich
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=5167D667.8020409@linux.vnet.ibm.com \
--to=lilei@linux.vnet.ibm.com \
--cc=marian.krucina@linuxbox.cz \
--cc=nikola.ciprich@linuxbox.cz \
--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.