From: "Daniel P. Berrange" <berrange@redhat.com>
To: Daniel Espling <setomidor@gmail.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] unknown keycodes
Date: Mon, 16 Jan 2012 11:34:23 +0000 [thread overview]
Message-ID: <20120116113423.GH19960@redhat.com> (raw)
In-Reply-To: <0AA7ECDD-7A44-4D02-B95C-1D741A0FF925@gmail.com>
On Mon, Jan 16, 2012 at 08:04:32AM +0100, Daniel Espling wrote:
> Hi Daniel,
>
> please find the output of xdpyinfo and xprop attached, I checked the output from both the linux server side and the OSX client, but the only difference is the "name of display" parameter so I included only that of the linux server.
>
> Regards,
> Daniel
> number of extensions: 23
> Apple-DRI
> Apple-WM
Good, those are the interesting bits I wanted to see
> _XKB_RULES_NAMES(STRING) = "base", "empty", "empty", "", ""
I'll prepare a patch to test out which ought to fix OS-X
Regards,
Daniel
--
|: http://berrange.com -o- http://www.flickr.com/photos/dberrange/ :|
|: http://libvirt.org -o- http://virt-manager.org :|
|: http://autobuild.org -o- http://search.cpan.org/~danberr/ :|
|: http://entangle-photo.org -o- http://live.gnome.org/gtk-vnc :|
next prev parent reply other threads:[~2012-01-16 11:34 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-12 8:56 [Qemu-devel] unknown keycodes Daniel Espling
2012-01-12 10:41 ` Daniel P. Berrange
2012-01-16 7:04 ` Daniel Espling
2012-01-16 11:34 ` Daniel P. Berrange [this message]
2013-05-07 21:02 ` Ali
-- strict thread matches above, loose matches on Subject: below --
2018-04-21 9:27 Mike R
2018-04-23 3:31 ` Thomas Huth
2018-04-23 9:10 ` Peter Maydell
2018-04-23 9:42 ` Daniel P. Berrangé
2018-04-23 9:44 ` Daniel P. Berrangé
2015-04-16 9:44 Daniel Moyle
2011-01-19 1:22 Henry Grebler
2011-01-19 1:45 ` Anthony Liguori
2009-06-21 8:56 [Qemu-devel] Unknown keycodes annonygmouse
2009-06-22 19:30 ` Anthony Liguori
2009-06-22 19:58 ` Andreas Färber
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=20120116113423.GH19960@redhat.com \
--to=berrange@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=setomidor@gmail.com \
/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.