Re: [Qemu-devel] Unknown X11 keycode mapping report

[Daniel P . Berrangé]

On Tue, Apr 02, 2019 at 02:47:25PM +0200, Jean-Louis SOLATGES wrote:
> Bonjour, par tightvnc server sur clipper depuis un linux connecté en 
> vncviewer,
> 
> je lance :
> qemu-system-x86_64 -m 16G -cpu kvm64 -accel kvm,thread=multi -smp 
> 6,maxcpus=12 -net nic -net tap -net socket,listen=127.0.0.1:1234 -vga cirrus 
> -boot c -hda uis1.img
> 
> 
> 
> address@hidden:/home/jls/data# ** (qemu-system-x86_64:16384): WARNING **: 
> Unknown X11 keycode mapping '<null>'.
> bash: syntax error near unexpected token `qemu-system-x86_64:16384'
> 
> -- 
> jls** (qemu-system-x86_64:16384): WARNING **: Unknown X11 keycode mapping 
> '<null>'.
> Please report to address@hidden
> including the following information:
> 
>   - Operating system
>   - X11 Server
>   - xprop -root
>   - xdpyinfo
> 
> ::::
> Linux clipper 4.4.14 #2 SMP Fri Jun 24 13:38:27 CDT 2016 x86_64 Intel(R) 
> Xeon(R) CPU           E5645  @ 2.40GHz GenuineIntel GNU/Linux
> 
> 
> 
> X.Org X Server 1.18.3
> Release Date: 2016-04-04
> X Protocol Version 11, Revision 0
> Build Operating System: Slackware 14.2 Slackware Linux Project
> Current Operating System: Linux clipper 4.4.14 #2 SMP Fri Jun 24 13:38:27 CDT 
> 2016 x86_64
> Kernel command line: auto BOOT_IMAGE=Linux ro root=801 vt.default_utf8=0
> Build Date: 15 April 2016  11:05:21AM
>  
> Current version of pixman: 0.34.0
>         Before reporting problems, check http://wiki.x.org
>         to make sure that you have the latest version.
> 
> 
> 
> address@hidden:/home/jls/data# xprop -root
> CUT_BUFFER0(STRING) = "address@hidden:/home/jls/data# xprop 
> -root\nCUT_BUFFER0(STRING) = \"address@hidden:/home/jls/data# name of 
> display:    :1\\nbash: name: command not address@hidden:/home/jls/data# 
> version number:    11.0\\nbash: version: command not found\\n\""


So there's no _XKB_RULES_NAMES property set which is what QEMU
wants to see.

> 
> address@hidden:/home/jls/data# xdpyinfo 
> name of display:    :1
> version number:    11.0
> vendor string:    AT&T Laboratories Cambridge
> vendor release number:    3332
> maximum request size:  4194300 bytes
> motion buffer size:  256
> bitmap unit, bit order, padding:    32, LSBFirst, 32
> image byte order:    LSBFirst
> number of supported pixmap formats:    2
> supported pixmap formats:supported pixmap formats:
>     depth 1, bits_per_pixel 1, scanline_pad 32
>     depth 24, bits_per_pixel 32, scanline_pad 32
> keycode range:    minimum 8, maximum 255
> focus:  PointerRoot
> number of extensions:    7
>     BIG-REQUESTS
>     MIT-SHM
>     MIT-SUNDRY-NONSTANDARD
>     SHAPE
>     SYNC
>     XC-MISC
>     XTEST

The  XKEYBOARD extension is missing which is why we dont' see the
XKB property above.

We have a heuristic that tries to deal with this by checking what
keycode  "XK_Page_Up" maps to, but that has failed for you too.

So I'm puzzlled what key map this X server is actually using.


I don't have SLackware handy, but can't reproduce on Fedora with
TigerVNC.

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