Hello Daniel,
I guess it is time for me to commit
suicide...when you dont think about the basics : software version :-(
Was 1.0.4, moved to 1.1.0, no issue
DONT BECOME OLD ! :-)
thanks!
At 10:42 13/05/2020, Daniel P. Berrangé wrote:
On Wed, May 13, 2020 at 10:38:52AM +0200, B3r3n wrote
know how to force noVNC keycodes instead, digging to find the trick :-(
Thanks
Brgrds
At 11:11 12/05/2020, Daniel P. Berrangé wrote:
On Tue, May 12, 2020 at 09:45:20AM +0200, B3r3n wrote:
> Hello Daniel, all,
>
> I am a bit confused.
>
> Ok, RFB protocol should be the solution
Dear all,
VNC == RFB - they're two different terms of the same thing.
The core RFB/VNC protocol only knows about keysyms.
Ok, so RFB is not the keyword to track :-(
AFAIK, TightVNC doesn't support the scancode extension, only TigerVNC.
Confirmed, I replaced TightVNC viewer by TigerVNC, solv
Hello Daniel, all,
I am a bit confused.
Ok, RFB protocol should be the solution that solves all, sending
scancodes rather than doing keysyms stuff. No pb for me.
So I removed my '-k fr' to my Qemu VM start as it was before.
However, reading TightVNC & noVNC docs, both are able to perform RFB.
Hello Daniel,
There is no mention here of what VNC client program is being used, which
is quite important, as key handling is a big mess in VNC.
I tested with TightVNC & noVNC through Apache. Both behaves the same.
I did not tested Ultr@VNC.
The default VNC protocol passes X11 keysyms over
