Re: gtk-vnc-WARNING **: unknown keycodes `empty_aliases(qwerty)'
- From: "Daniel P. Berrange" <dan berrange com>
- To: "Richard W.M. Jones" <rjones redhat com>
- Cc: gtk-vnc-devel List <gtk-vnc-list gnome org>
- Subject: Re: gtk-vnc-WARNING **: unknown keycodes `empty_aliases(qwerty)'
- Date: Sat, 3 Jul 2010 22:08:30 +0100
On Thu, Jul 01, 2010 at 09:54:55PM +0100, Richard W.M. Jones wrote:
> On Thu, Jul 01, 2010 at 09:42:33PM +0100, Daniel P. Berrange wrote:
> > On Thu, Jul 01, 2010 at 09:23:44PM +0100, Richard W.M. Jones wrote:
> > > On Thu, Jul 01, 2010 at 02:55:36PM -0500, Anthony Liguori wrote:
> > > > On 07/01/2010 02:44 PM, Richard W.M. Jones wrote:
> > > >> As the error message says ...
> > > >>
> > > >>
> > > >>> # virt-viewer RHEL6beta2x64
> > > >>> Xlib: extension "RANDR" missing on display "localhost:10.0".
> > > >>>
> > > >>> (virt-viewer:17347): gtk-vnc-WARNING **: unknown keycodes `empty_aliases(qwerty)', please report to gtk-vnc-devel
> > > >>>
> > > >> So you'll probably want to know what X server this is, etc:
> > > >>
> > > >> The server is XQuartz 2.5.0 (xorg-server 1.7.6) on Mac OS X 10.5.8 x86_64.
> > > >>
> > > >
> > > > Could you share the qwerty keycode file for the server?
> > > >
> > > > On Linux, it would be located in /usr/share/X11/xkb/keycodes/qwerty
> > >
> > > The directory 'keycodes' doesn't contain a file called 'qwerty' at
> > > all:
> >
> > When it gets this scenario, we default to just using the xfree86
> > standard keymap. If you connect to a QEMU guest VNC server, do
> > all the keys appear to be passing through correctly ? In particular
> > check arrow keys, pageup/pagedown & other non-alphanumeric keys.
> > Perhaps we'll be lucky and find qwerty can just use the existing
> > maps
>
> This doesn't appear to affect operations at all. Arrow keys,
> ctrl key etc all seem to work.
I must say I'm very puzzled how it is working correctly, unless the QEMU
instance you connected virt-viewer to had the '-k' option set with a
keymap. I've looked at the XQuartz code now and it has its own native
keyboard driver, and the hardware keycode I believe we'd get is using
the Apple virtual keycode mappings which is nothing like the xfree86 or
evdev mappings. On the plus side I know understand our key handling code
much better than I did before :-)
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 :|
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]