Gerd Hoffmann writes:
> Hi,
>
>>> What is your vnc client? Does it support VNC_ENCODING_EXT_KEY_EVENT?
>>
>> It's uses gvnc as a protocol library and renders via fbdev. It reads
>> keyboard events by putting /dev/tty into mediumraw mode and uses ext key
>> events exclusively. It has no know
Hi,
>> What is your vnc client? Does it support VNC_ENCODING_EXT_KEY_EVENT?
>
> It's uses gvnc as a protocol library and renders via fbdev. It reads
> keyboard events by putting /dev/tty into mediumraw mode and uses ext key
> events exclusively. It has no knowledge of the guest keymap.
Neat
Gerd Hoffmann writes:
> On 04/15/13 16:41, Anthony Liguori wrote:
>> Gerd Hoffmann writes:
>>
>>> Hi,
>>>
When access a guest by console through VNC, there might be
mismatch between the lock keys notification LED on the computer
running the VNC client session and the current st
On 04/15/13 16:41, Anthony Liguori wrote:
> Gerd Hoffmann writes:
>
>> Hi,
>>
>>> When access a guest by console through VNC, there might be
>>> mismatch between the lock keys notification LED on the computer
>>> running the VNC client session and the current status of the lock
>>> keys on the
Gerd Hoffmann writes:
> Hi,
>
>> When access a guest by console through VNC, there might be
>> mismatch between the lock keys notification LED on the computer
>> running the VNC client session and the current status of the lock
>> keys on the guest machine. This happens because the VNC protocol
Hi,
> When access a guest by console through VNC, there might be
> mismatch between the lock keys notification LED on the computer
> running the VNC client session and the current status of the lock
> keys on the guest machine. This happens because the VNC protocol
> does not have any support to
