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:
>
On Wed, May 13, 2020 at 10:38:52AM +0200, B3r3n wrote:
> Hello Daniel,
>
> Ok, TigerVNC, added -shared=1 to behave the same as TightVNC, works greatly,
> Thanks !
>
> But funny thing, I saw you were part of exchanges on that topic, noVNC
> totally fails now.
> Despite my keyboard isnt changed, de
Hello Daniel,
Ok, TigerVNC, added -shared=1 to behave the same
as TightVNC, works greatly, Thanks !
But funny thing, I saw you were part of exchanges
on that topic, noVNC totally fails now.
Despite my keyboard isnt changed, debian VM is
just in QWERTY as if noVNC only send keysyms.
If you
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
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 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.
>
>
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
On Mon, May 11, 2020 at 05:29:48PM +0200, B3r3n wrote:
> 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 te
On Mon, May 11, 2020 at 04:24:32PM +0200, Philippe Mathieu-Daudé wrote:
> Cc'ing more developers.
>
> On 5/11/20 4:17 PM, B3r3n wrote:
> > Dear all,
> >
> > I am struggling for days/weeks with Qemu and its VNC accesses...with
> > non-US keymaps.
> >
> > Let me summ the facts:
> > - I am using a
I have a similar problem with qemu (all versions including 5.0.0) on
MacOS-10.14.6 (mac book pro 2017with touch bar).
Using -k fr-mac the "@"/"#" key is dead.
Showkey doesn't detect the key.
Moreover, the # and @ symbols are mapped on the "<" / ">" key and thus I miss
the redirection operator in
Cc'ing more developers.
On 5/11/20 4:17 PM, B3r3n wrote:
Dear all,
I am struggling for days/weeks with Qemu and its VNC accesses...with
non-US keymaps.
Let me summ the facts:
- I am using a french keyboard over a Ubuntu 18.04.
- I installed a simple Debian in a Qemu VM, configured with FR ke
11 matches
Mail list logo
