qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Gerd Hoffmann <kraxel@redhat.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: Tue, 16 Apr 2013 08:34:32 +0200	[thread overview]
Message-ID: <516CF0F8.2060709@redhat.com> (raw)
In-Reply-To: <20130415154335.GX28496@pcnci.linuxbox.cz>

On 04/15/13 17:43, Nikola Ciprich wrote:
> Hi Gerd,
> 
> I'm using tigervnc, but the problem occurs also with xrdp vnc2rdp
> proxy..

Do things improve with a gtk-vnc based client?  vinagre or
remote-viewer (comes bundles with recent virt-viewer versions)?

cheers,
  Gerd

  reply	other threads:[~2013-04-16  6:34 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
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 [this message]
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=516CF0F8.2060709@redhat.com \
    --to=kraxel@redhat.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 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).