From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:51053) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1eP3Od-0006lE-6q for qemu-devel@nongnu.org; Wed, 13 Dec 2017 04:32:12 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1eP3OX-00061F-7n for qemu-devel@nongnu.org; Wed, 13 Dec 2017 04:32:11 -0500 Received: from mx1.redhat.com ([209.132.183.28]:33738) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1eP3OX-00060A-1e for qemu-devel@nongnu.org; Wed, 13 Dec 2017 04:32:05 -0500 Date: Wed, 13 Dec 2017 09:31:58 +0000 From: "Daniel P. Berrange" Message-ID: <20171213093158.GC28379@redhat.com> Reply-To: "Daniel P. Berrange" References: <20171211122936.GA2422@work-vm> <20171211123317.GB23622@redhat.com> <20171211150841.GE23622@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <20171211150841.GE23622@redhat.com> Subject: Re: [Qemu-devel] It told me to report this... List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Warner Losh Cc: qemu-devel@nongnu.org, "Dr. David Alan Gilbert" , kraxel@redhat.com On Mon, Dec 11, 2017 at 03:08:41PM +0000, Daniel P. Berrange wrote: > On Mon, Dec 11, 2017 at 08:05:29AM -0700, Warner Losh wrote: > > On Mon, Dec 11, 2017 at 5:33 AM, Daniel P. Berrange > > wrote: > > > > > On Mon, Dec 11, 2017 at 12:29:36PM +0000, Dr. David Alan Gilbert wrote: > > > > * Warner Losh (imp@bsdimp.com) wrote: > > > > > unknown keycodes `empty+aliases(qwerty)', please report to > > > > > qemu-devel@nongnu.org > > > > > > > > > > My X server is Mac XQuartz 2.7.11. I saw this question raised several > > > years > > > > > ago in the archives, with promises of patches, but couldn't find > > > anything > > > > > relevant in the latest tree I grabbed from github (I saw this problem > > > there > > > > > as well as 2.9.0 installed from FreeBSD ports). > > > > > > > > > > What's my next step here? > > > > > > > > I think that's one of Gerd's messages, so I've added him to the > > > > email and also Daniel since he's got an interest in key mappings. > > > > > > > > Have you any idea if it happened when you pressed a particular key? > > > > > > Don't worry, this is a known limitation of the current X backend for QEMU. > > > > > > It only knows how to work with Xorg on Linux with kbd or evdev. It can't > > > cope with OS-X or Windows X11 servers yet. I've got patches that will > > > address this which i hope to finally put into 2.12 as part of the > > > keycodemapdb > > > work. > > > > > > > I've built qemu many times over the years. I'd be happy to test them out to > > make sure they work for me :). Also, a million years ago, I did extensive > > work with X11 keymaps when I was working on the OI toolkit, so I have some > > familiarity... > > I'm basically copying the same code / approach we've already done with > GTK-VNC & SPICE-GTK > > I've got a patch here: > > https://lists.gnu.org/archive/html/qemu-devel/2017-08/msg02058.html > > but that almost certainly won't apply to current GIT master, so I'll be > sending updated versions soonish. If you want to test something, then I've posted new patch series with the UI changes: https://lists.gnu.org/archive/html/qemu-devel/2017-12/msg01988.html it applies to current git master, aka soon to be 2.11. 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 :|