On 8/17/2018 11:51 AM, Daniel P. Berrangé wrote:
> Since you're using tightvnc on Windows, it won't be using the raw scancode
> extension to RFB, so it'll be sending X keysyms across the wire eg
>
> "|" has X11 keysym 0x7c (XK_bar)
> "\" has X11 keysym 0x5c (XK_backslash)
>
> First thing
On Mon, Aug 20, 2018 at 9:51 PM Phillip Susi wrote:
> On 8/20/2018 11:07 AM, Christian Ehrhardt wrote:
> > What exactly would you need in Ubuntu Phillp?
>
> It *looks* like this is fixed in 2.12, but Ubuntu has 2.11.
>
> > Latest qemu would atm be on 2.12 with the git available here [1].
> >
On 8/20/2018 11:07 AM, Christian Ehrhardt wrote:
> What exactly would you need in Ubuntu Phillp?
It *looks* like this is fixed in 2.12, but Ubuntu has 2.11.
> Latest qemu would atm be on 2.12 with the git available here [1].
> Unfortunately mostly nobody cares about the git branches so I forgot
On Mon, Aug 20, 2018 at 4:32 PM Phillip Susi wrote:
> On 8/20/2018 4:43 AM, Gerd Hoffmann wrote:
> > There have been fixes for that one, specifically recent qemu will look
> > at modifier state in addition to the keysym when looking up the keycode,
> > because some keymaps can generate the same
On 8/20/2018 4:43 AM, Gerd Hoffmann wrote:
> There have been fixes for that one, specifically recent qemu will look
> at modifier state in addition to the keysym when looking up the keycode,
> because some keymaps can generate the same keysym with different key
> combinations, and most of the time
On Fri, Aug 17, 2018 at 11:16:29AM -0400, Phillip Susi wrote:
> On 8/17/2018 11:05 AM, Daniel P. Berrangé wrote:
> > Reading again, this is a bit odd. On most keyboards, holding down shift
> > key generally would NOT change the scan code that is reported (there are a
>
> Right; a real keyboard
On 8/17/2018 11:05 AM, Daniel P. Berrangé wrote:
> Reading again, this is a bit odd. On most keyboards, holding down shift
> key generally would NOT change the scan code that is reported (there are a
Right; a real keyboard won't change the scan code, but it seems that
European keyboards have this
On Fri, Aug 17, 2018 at 11:16:29AM -0400, Phillip Susi wrote:
> On 8/17/2018 11:05 AM, Daniel P. Berrangé wrote:
> > Reading again, this is a bit odd. On most keyboards, holding down shift
> > key generally would NOT change the scan code that is reported (there are a
>
> Right; a real keyboard
On Fri, Aug 17, 2018 at 03:44:21PM +0100, Daniel P. Berrangé wrote:
> On Fri, Aug 17, 2018 at 10:36:14AM -0400, Phillip Susi wrote:
> > I've been reading up here:
> > http://www.win.tue.nl/~aeb/linux/kbd/scancodes-1.html
> >
> > And man, what a mess keyboards are! Worse than floppy controllers.
On Thu, Aug 16, 2018 at 01:11:05PM -0400, Phillip Susi wrote:
> Hello, I recently upgraded my Xen server from Ubuntu 16.04 to 18.04 and
> am no longer able to type a | over vnc to the xen vms. When I press \
> it works, but when I hold down shift and press \ which should generate a
> |, the vm
I've been reading up here:
http://www.win.tue.nl/~aeb/linux/kbd/scancodes-1.html
And man, what a mess keyboards are! Worse than floppy controllers.
According to that site, the scan code for \ should be 0x2b, so why does
xev say the keycode is 51? Is keycode something else entirely from scan
On 8/17/2018 10:44 AM, Daniel P. Berrangé wrote:
> 0x2b is 43 in hex.
>
> xev reports the Xorg scancode, which is the same as the XT/AT-set1
> scancodes, with an offset of 8 added
>
> IOW, 51 from xev does actually match 0x2b from XT scancode set
Oy vey! Just for fun they decided to add 8 eh?
On Fri, Aug 17, 2018 at 10:36:14AM -0400, Phillip Susi wrote:
> I've been reading up here:
> http://www.win.tue.nl/~aeb/linux/kbd/scancodes-1.html
>
> And man, what a mess keyboards are! Worse than floppy controllers.
> According to that site, the scan code for \ should be 0x2b, so why does
>
On 8/17/2018 9:12 AM, Daniel P. Berrangé wrote:
> It depends on what the VNC client asks for too. With no '-k' arg, if the
> VNC client asks for raw scancodes it'll get that, otherwise QEMU will
> fallback to en-US.GTK-VNC based clients (remote-viewer, virt-viewer,
> vinagre, virt-manager,
On Fri, Aug 17, 2018 at 09:10:54AM -0400, Phillip Susi wrote:
> On 8/17/2018 8:58 AM, Daniel P. Berrangé wrote:
> > Actually for QEMU there is no default localized keymap. This is desirable
> > because it allows VNC to activate its raw scancode extension which is more
> > reliable than passing
On 8/17/2018 8:58 AM, Daniel P. Berrangé wrote:
> Actually for QEMU there is no default localized keymap. This is desirable
> because it allows VNC to activate its raw scancode extension which is more
> reliable than passing translated X11 key symbols.
>
> I guess there's a chance that Xen might
On Fri, Aug 17, 2018 at 08:44:36AM -0400, Phillip Susi wrote:
> On 8/17/2018 4:56 AM, Daniel P. Berrangé wrote:
> > Oh one other thing, is whether your QEMU process has an explicit keymap
> > configured (this is the -k arg to QEMU), as when that it set, it
> > completely changes the way keyboard
On Thu, Aug 16, 2018 at 01:11:05PM -0400, Phillip Susi wrote:
> Hello, I recently upgraded my Xen server from Ubuntu 16.04 to 18.04 and
> am no longer able to type a | over vnc to the xen vms. When I press \
> it works, but when I hold down shift and press \ which should generate a
> |, the vm
On 8/17/2018 4:56 AM, Daniel P. Berrangé wrote:
> Oh one other thing, is whether your QEMU process has an explicit keymap
> configured (this is the -k arg to QEMU), as when that it set, it
> completely changes the way keyboard input is handled in VNC. That code
> has also been massively refactored
On Thu, Aug 16, 2018 at 03:44:54PM -0400, Phillip Susi wrote:
> On 8/16/2018 1:27 PM, Daniel P. Berrangé wrote:
> > Did you actually 'git bisect' to that commit, or is that just a guess ?
>
> No, I haven't actually tried to build it from sources myself yet so I
> just found the source file that
On 8/16/2018 1:27 PM, Daniel P. Berrangé wrote:
> Did you actually 'git bisect' to that commit, or is that just a guess ?
No, I haven't actually tried to build it from sources myself yet so I
just found the source file that handles the keyboard, saw a bunch of
scancode translation stuff in it,
On Thu, Aug 16, 2018 at 01:11:05PM -0400, Phillip Susi wrote:
> Hello, I recently upgraded my Xen server from Ubuntu 16.04 to 18.04 and
> am no longer able to type a | over vnc to the xen vms. When I press \
> it works, but when I hold down shift and press \ which should generate a
> |, the vm
Hello, I recently upgraded my Xen server from Ubuntu 16.04 to 18.04 and
am no longer able to type a | over vnc to the xen vms. When I press \
it works, but when I hold down shift and press \ which should generate a
|, the vm sees the scan code for some key that the keymap thinks should
sit
23 matches
Mail list logo
