All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Phillip Susi <psusi@ubuntu.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Pipe key broken on US keyboards
Date: Thu, 16 Aug 2018 18:27:22 +0100	[thread overview]
Message-ID: <20180816172722.GK23515@redhat.com> (raw)
In-Reply-To: <bf97cfed-ca7f-8670-0aad-da1b847eb609@ubuntu.com>

On Thu, Aug 16, 2018 at 01:11:05PM -0400, Phillip Susi wrote:
> Hello, I recently upgraded my Xen server from Ubuntu 16.04 to 18.04 and
> am no longer able to type a | over vnc to the xen vms.  When I press \
> it works, but when I hold down shift and press \ which should generate a
> |, the vm sees the scan code for some key that the keymap thinks should
> sit between left shift and Z, but does not exist on US keyboards, and
> that scan code produces a > when combined with shift.  I'm betting it
> was this commit that broke it:
> 
> commit ab8f9d49d62c82a12409475547e4420a46da56ed
> Author: Daniel P. Berrange <berrange@redhat.com>
> Date:   Wed Jan 17 16:41:15 2018 +0000
> 
>     hw: convert ps2 device to keycodemapdb
> 
>     Replace the qcode_to_keycode_set1, qcode_to_keycode_set2,
>     and qcode_to_keycode_set3 tables with automatically
>     generated tables.
> 
> Any ideas?

Did you actually 'git bisect' to that commit, or is that just a guess ?

If not, could you 'git bisect' to confirm the actual commit, as there
have been lots of changes in this area.


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 :|

  reply	other threads:[~2018-08-16 17:27 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-16 17:11 [Qemu-devel] Pipe key broken on US keyboards Phillip Susi
2018-08-16 17:27 ` Daniel P. Berrangé [this message]
2018-08-16 19:44   ` Phillip Susi
2018-08-17  8:56     ` Daniel P. Berrangé
2018-08-17 12:44       ` Phillip Susi
2018-08-17 12:58         ` Daniel P. Berrangé
2018-08-17 13:10           ` Phillip Susi
2018-08-17 13:12             ` Daniel P. Berrangé
2018-08-17 13:23               ` Phillip Susi
2018-08-17 14:36               ` Phillip Susi
2018-08-17 14:44                 ` Daniel P. Berrangé
2018-08-17 14:55                   ` Phillip Susi
2018-08-17 15:06                   ` Daniel P. Berrangé
2018-08-17 12:56 ` Daniel P. Berrangé
2018-08-17 15:05 ` Daniel P. Berrangé
2018-08-17 15:16   ` Phillip Susi
2018-08-17 15:51     ` Daniel P. Berrangé
2018-08-21 19:35       ` Phillip Susi
2018-08-20  8:43     ` Gerd Hoffmann
2018-08-20 14:23       ` Phillip Susi
2018-08-20 15:07         ` Christian Ehrhardt
2018-08-20 19:51           ` Phillip Susi
2018-08-20 20:04             ` Christian Ehrhardt

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=20180816172722.GK23515@redhat.com \
    --to=berrange@redhat.com \
    --cc=psusi@ubuntu.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.