From: B3r3n <B3r3n@argosnet.com>
To: "Daniel P. Berrangé" <berrange@redhat.com>
Cc: "Philippe Mathieu-Daudà ? ? à ? é" <philmd@redhat.com>,
qemu-devel <qemu-devel@nongnu.org>,
"Gerd Hoffmann" <kraxel@redhat.com>,
qemu-discuss@nongnu.org
Subject: Re: Qemu, VNC and non-US keymaps
Date: Wed, 13 May 2020 11:13:45 +0200 [thread overview]
Message-ID: <E1jYnSZ-0001j9-F0@lists.gnu.org> (raw)
In-Reply-To: <20200513084257.GC1215285@redhat.com>
Hello Daniel,
I guess it is time for me to commit
suicide...when you dont think about the basics : software version :-(
Was 1.0.4, moved to 1.1.0, no issue
DONT BECOME OLD ! :-)
thanks!
At 10:42 13/05/2020, Daniel P. Berrangé wrote:
>On Wed, May 13, 2020 at 10:38:52AM +0200, B3r3n wrote:
> > Hello Daniel,
> >
> > Ok, TigerVNC, added -shared=1 to behave the
> same as TightVNC, works greatly,
> > Thanks !
> >
> > But funny thing, I saw you were part of exchanges on that topic, noVNC
> > totally fails now.
> > Despite my keyboard isnt changed, debian VM is just in QWERTY as if noVNC
> > only send keysyms.
> >
> > If you know how to force noVNC keycodes
> instead, digging to find the trick :-(
>
>Looking at the current git master code AFAICT it should "just work"
>unless you have an older version of it perhaps
>
>
>Regards,
>Daniel
>--
>|: https://berrange.com -o- https://www.flickr.com/photos/dberrange :|
>|: https://libvirt.org -o- https://fstop138.berrange.com :|
>|: https://entangle-photo.org -o- https://www.instagram.com/dberrange :|
prev parent reply other threads:[~2020-05-13 9:14 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E1jY9FF-0000Po-2c@lists.gnu.org>
2020-05-11 14:24 ` Qemu, VNC and non-US keymaps Philippe Mathieu-Daudé
2020-05-11 14:31 ` LAHAYE Olivier
2020-05-11 15:11 ` Daniel P. Berrangé
2020-05-11 15:29 ` B3r3n
[not found] ` <20200511152957.6CFA8D1826@zmta04.collab.prod.int.phx2.redhat.com>
2020-05-11 17:19 ` Daniel P. Berrangé
2020-05-12 7:45 ` B3r3n
[not found] ` <20200512074530.8729D1892D3@zmta01.collab.prod.int.phx2.redhat.com>
2020-05-12 9:11 ` Daniel P. Berrangé
2020-05-12 16:30 ` B3r3n
2020-05-13 8:38 ` B3r3n
2020-05-13 8:42 ` Daniel P. Berrangé
2020-05-13 9:13 ` B3r3n [this message]
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=E1jYnSZ-0001j9-F0@lists.gnu.org \
--to=b3r3n@argosnet.com \
--cc=berrange@redhat.com \
--cc=kraxel@redhat.com \
--cc=philmd@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-discuss@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.