Can not type pipe '|' key via unraid vnc

[iga 1]

Hi guys,

 

I have a few linux vms created with unraid and I am struggling to find a way to type pipe(|) in terminal via unraid vnc, either the browser version of novnc or tightvnc viewer. the keyboard mapping are all default to us keyboard, they all turn '|' to '>' for either lubuntu, manjaro or mxlinux.

 

when I ssh in, everything works just fine.

 

Could anyone give some suggestions?

[juanamingo 1]

I'm having the same issue and not only does typing the '|' character ('shift + \' ) produce '>' and not the expected '|'  but the '<' key ('shift + ,') also produces '>' and not the expected '<'.  typing the non-shifted characters works fine, \ and ,

 

I've tried the browser vnc, tight vnc and tiger vnc.

 

unraid 6.5.3

 

arch linux typing 'SHIFT + \' produces '>' and 'SHIFT + <' produces '>'

ubuntu 14.04 typing 'SHIFT + \' produces '>' and 'SHIFT + <' produces '>'

 

osx high sierra both 'SHIFT + \' and 'SHIFT +' , produce a '+' over top a '_' (a "plus-minus" symbol if you will)

 

windows 10 - the '\' and '|' can be typed fine, but 'SHIFT + ,' produce '|' instead of '<' and 'SHIFT + .' produce '|' instead of '>'

 

If any logs or anything are needed, please lmk

Edited August 3, 2018 by juanamingo

[bubo 4]

I am also experiencing the same issue reported here.

 

 

ubuntu 16.04 typing 'SHIFT + \' produces '>' and 'SHIFT + <' produces '>'

 

I was setting up a new server when I experienced this issue.  I then tried booting an existing Ubuntu server that I've used for 2 years, initially setup in an unRAID VM with no issues with the pipe character.  When trying to type a pipe character, this old server also produced a > instead of |.  This appears to be an issue with either unRAID, or more likely the noVNC being used.

 

[eschultz 95]

These keyboard issues are solved in the upcoming unRAID 6.6 -- it includes an updated version of QEMU that has the keyboard mappings fixed.

[bubo 4]

OK, thank you for the quick answer.  6.5.3-rc2 is out now, so I believe 6.6 is currently being worked on?

 

Until 6.6 is ready, does anyone have a workaround that can be employed?

[bonienl 1089]

Latest official version is 6.5.3.

rc = release candidate and is mainly used for testing purposes, please update if you are still on a rc release.

 

[cybrnook 92]

18 hours ago, eschultz said:

These keyboard issues are solved in the upcoming unRAID 6.6 -- it includes an updated version of QEMU that has the keyboard mappings fixed.

Super excited for this.

[cybrnook 92]

On 8/5/2018 at 1:16 AM, eschultz said:

These keyboard issues are solved in the upcoming unRAID 6.6 -- it includes an updated version of QEMU that has the keyboard mappings fixed.

Is 6.6 anywhere close to going to the RC phase?

[eschultz 95]

Probably in a week.  QEMU 3.0 was just released so we'll get that in to the public unRAID 6.6-rc release too.

[Xaero 99]

5 hours ago, eschultz said:

Probably in a week.  QEMU 3.0 was just released so we'll get that in to the public unRAID 6.6-rc release too.

Any chance that includes the HTML5 SPICE client and SPICE integration?
Spice is way more cohesive to a VM than VNC is.

[cybrnook 92]

On 8/18/2018 at 4:02 PM, eschultz said:

Probably in a week.  QEMU 3.0 was just released so we'll get that in to the public unRAID 6.6-rc release too.

Confirmed working great in 6.6-rc1 |||||||||| 🙂 

[BlueSialia 0]

Hello,

 

Was this bug reintroduced at some point?

 

I'm using unRAID 6.8.3 and I have this issue.

[Dtrain 1]

can report same issue --- not working with 6.83