display=1920x1080
clienthostname=TESTAR_SWM
wtrc=on
language=sv, default
keyboard=sv
connection
server=xxxxxxxxxxxxxxxxxxxxx
connection
displayName=xxxxxxxxxxxxxxxxxxxx
server=VNC:172.21.179.210
user=anything:xxxxxxxxxxxxxxx
connection
application=chrome
keyboard_log=on
Language problems in VNC, Terminal login and Chrome #swedish
Language problems in VNC, Terminal login and Chrome #swedish
I can´t get swedish language working with the following settings on v 6.2.42.
Re: Language problems in VNC, Terminal login and Chrome #swedish
This is an urgent request on 20 payed licenses. Please respond as soon as possible.
Re: Language problems in VNC, Terminal login and Chrome #swedish
1. Where do you want to get swedish language? Show screen photo of interface you need.
2. Please find right keyboard layout for swedish language here: http://kbdlayout.info/
2. Please find right keyboard layout for swedish language here: http://kbdlayout.info/
Re: Language problems in VNC, Terminal login and Chrome #swedish
Thank you for the quick respons!
1. Can´t attach image but it´s in wtware terminal view and when connecting to VNC (vncclient_keyboard)
2. https://kbdlayout.info/kbdsw
keylog for åäö:
#å#
11-58-44-511| [ gm] [ 389.660334] [WTRC keyboard] Scan 0x1a => WT_KEY_SQR_BRACKET_L.
11-58-44-553| [ gm] [ 389.660541] Key WT_KEY_SQR_BRACKET_L (79) pressed.
11-58-44-620| [ gm] [ 389.769628] [WTRC keyboard] Scan 0x1a => WT_KEY_SQR_BRACKET_L.
11-58-44-661| [ gm] [ 389.769934] Key WT_KEY_SQR_BRACKET_L (79) released.
#ä#
11-58-44-871| [ gm] [ 390.020244] [WTRC keyboard] Scan 0x28 => WT_KEY_APOSTROPHE.
11-58-44-913| [ gm] [ 390.020363] Key WT_KEY_APOSTROPHE (99) pressed.
11-58-44-992| [ gm] [ 390.141210] [WTRC keyboard] Scan 0x28 => WT_KEY_APOSTROPHE.
11-58-45-034| [ gm] [ 390.141494] Key WT_KEY_APOSTROPHE (99) released.
#ö#
11-58-45-320| [ gm] [ 390.469513] [WTRC keyboard] Scan 0x27 => WT_KEY_SEMICOLON.
11-58-45-361| [ gm] [ 390.469675] Key WT_KEY_SEMICOLON (98) pressed.
11-58-45-454| [ gm] [ 390.604160] [WTRC keyboard] Scan 0x27 => WT_KEY_SEMICOLON.
11-58-45-497| [ gm] [ 390.604446] Key WT_KEY_SEMICOLON (98) released.
1. Can´t attach image but it´s in wtware terminal view and when connecting to VNC (vncclient_keyboard)
2. https://kbdlayout.info/kbdsw
keylog for åäö:
#å#
11-58-44-511| [ gm] [ 389.660334] [WTRC keyboard] Scan 0x1a => WT_KEY_SQR_BRACKET_L.
11-58-44-553| [ gm] [ 389.660541] Key WT_KEY_SQR_BRACKET_L (79) pressed.
11-58-44-620| [ gm] [ 389.769628] [WTRC keyboard] Scan 0x1a => WT_KEY_SQR_BRACKET_L.
11-58-44-661| [ gm] [ 389.769934] Key WT_KEY_SQR_BRACKET_L (79) released.
#ä#
11-58-44-871| [ gm] [ 390.020244] [WTRC keyboard] Scan 0x28 => WT_KEY_APOSTROPHE.
11-58-44-913| [ gm] [ 390.020363] Key WT_KEY_APOSTROPHE (99) pressed.
11-58-44-992| [ gm] [ 390.141210] [WTRC keyboard] Scan 0x28 => WT_KEY_APOSTROPHE.
11-58-45-034| [ gm] [ 390.141494] Key WT_KEY_APOSTROPHE (99) released.
#ö#
11-58-45-320| [ gm] [ 390.469513] [WTRC keyboard] Scan 0x27 => WT_KEY_SEMICOLON.
11-58-45-361| [ gm] [ 390.469675] Key WT_KEY_SEMICOLON (98) pressed.
11-58-45-454| [ gm] [ 390.604160] [WTRC keyboard] Scan 0x27 => WT_KEY_SEMICOLON.
11-58-45-497| [ gm] [ 390.604446] Key WT_KEY_SEMICOLON (98) released.
Re: Language problems in VNC, Terminal login and Chrome #swedish
Looks right here, but doesnt work when i type user/password when i´m in the login screen in wtware.
/--- FILE "/etc/xorg.conf" -----------------------
| Section "InputDevice"
| Identifier "InpDev_event2"
| Driver "evdev"
| Option "Device" "/dev/input/event2"
| Option "SendCoreEvents" "on"
| Option "XkbLayout" "se,us"
| Option "XkbOptions" "grp:ctrl_shift_toggle"
| EndSection
| Section "InputDevice"
| Identifier "InpDev_event3"
| Driver "evdev"
| Option "Device" "/dev/input/event3"
| Option "SendCoreEvents" "on"
| Option "XkbLayout" "se,us"
| Option "XkbOptions" "grp:ctrl_shift_toggle"
| EndSection
| Section "InputDevice"
| Identifier "InpDev_event4"
| Driver "evdev"
| Option "Device" "/dev/input/event4"
| Option "SendCoreEvents" "on"
| Option "XkbLayout" "se,us"
| Option "XkbOptions" "grp:ctrl_shift_toggle"
| EndSection
| Section "InputDevice"
| Identifier "InpDev_event5"
| Driver "evdev"
| Option "Device" "/dev/input/event5"
| Option "SendCoreEvents" "on"
| Option "XkbLayout" "se,us"
| Option "XkbOptions" "grp:ctrl_shift_toggle"
Also this when trying vnc (vncclient_keyboard=sv):
[ gm] [ 222.706354] Free ram before fork terminal client /sbin/vncclient (session 2): 7710876 Kb.
[ gm] [ 222.706567] Run '/sbin/vncclient 2', log '/tmp/rdpclient.out', env '', pid ''.
[ pfac] [ 222.706619] Run /sbin/vncclient 2.
[ pfac] [ 222.706859] Ok, PID 822.
[ vncclient 822] [ 222.715234] VNC Client, WTware 6.2.42/RPi64, pipe 2, pid 822.
[ vncclient 822] [ 222.715529] Use /usr/lib/ui32.so.
[ gm] [ 222.716614] Incorrect "vncclient_keyboard" parameter value.
[ vncclient 822] [ 222.716764] vncclient-main.cpp ( 52): -- ERROR -- INTERNAL ERROR. Please, contact WTware tech support.
[ vncclient 822] [ 222.716872] Oops, something went wrong.
[ vncclient 822] [ 222.716968] Caught signal SIGPIPE.
[ gm] [ 223.093124] Session is over. Final message: Incorrect "vncclient_keyboard" parameter value.
[ pfac] [ 223.093378] Process pid 822 terminated, status 00000009.
/--- FILE "/etc/xorg.conf" -----------------------
| Section "InputDevice"
| Identifier "InpDev_event2"
| Driver "evdev"
| Option "Device" "/dev/input/event2"
| Option "SendCoreEvents" "on"
| Option "XkbLayout" "se,us"
| Option "XkbOptions" "grp:ctrl_shift_toggle"
| EndSection
| Section "InputDevice"
| Identifier "InpDev_event3"
| Driver "evdev"
| Option "Device" "/dev/input/event3"
| Option "SendCoreEvents" "on"
| Option "XkbLayout" "se,us"
| Option "XkbOptions" "grp:ctrl_shift_toggle"
| EndSection
| Section "InputDevice"
| Identifier "InpDev_event4"
| Driver "evdev"
| Option "Device" "/dev/input/event4"
| Option "SendCoreEvents" "on"
| Option "XkbLayout" "se,us"
| Option "XkbOptions" "grp:ctrl_shift_toggle"
| EndSection
| Section "InputDevice"
| Identifier "InpDev_event5"
| Driver "evdev"
| Option "Device" "/dev/input/event5"
| Option "SendCoreEvents" "on"
| Option "XkbLayout" "se,us"
| Option "XkbOptions" "grp:ctrl_shift_toggle"
Also this when trying vnc (vncclient_keyboard=sv):
[ gm] [ 222.706354] Free ram before fork terminal client /sbin/vncclient (session 2): 7710876 Kb.
[ gm] [ 222.706567] Run '/sbin/vncclient 2', log '/tmp/rdpclient.out', env '', pid ''.
[ pfac] [ 222.706619] Run /sbin/vncclient 2.
[ pfac] [ 222.706859] Ok, PID 822.
[ vncclient 822] [ 222.715234] VNC Client, WTware 6.2.42/RPi64, pipe 2, pid 822.
[ vncclient 822] [ 222.715529] Use /usr/lib/ui32.so.
[ gm] [ 222.716614] Incorrect "vncclient_keyboard" parameter value.
[ vncclient 822] [ 222.716764] vncclient-main.cpp ( 52): -- ERROR -- INTERNAL ERROR. Please, contact WTware tech support.
[ vncclient 822] [ 222.716872] Oops, something went wrong.
[ vncclient 822] [ 222.716968] Caught signal SIGPIPE.
[ gm] [ 223.093124] Session is over. Final message: Incorrect "vncclient_keyboard" parameter value.
[ pfac] [ 223.093378] Process pid 822 terminated, status 00000009.
Re: Language problems in VNC, Terminal login and Chrome #swedish
wtware interface
Re: Language problems in VNC, Terminal login and Chrome #swedish
Please try this build:
http://wtware.com/testing/202410292109/ ... .43.en.zip
In config:
Show me full log if it won't work: http://wtware.com/logs.html
http://wtware.com/testing/202410292109/ ... .43.en.zip
In config:
Code: Select all
language=sv,default
Re: Language problems in VNC, Terminal login and Chrome #swedish
Yes it works!
Can you do the same for vncclient_keyboard? >>>
[ gm] [ 18.651156] [WTRC] Connection from 172.21.170.243.
[ gm] [ 18.689507] [WTRC] Control password accepted.
[ gm] [ 18.690807] [WTRC] Zoom 75%, 2 bytes per pixel.
[ gm] [ 20.465144] Free ram before fork terminal client /sbin/vncclient (session 1): 7900424 Kb.
[ pfac] [ 20.465346] Run /sbin/vncclient 1.
[ gm] [ 20.465402] Run '/sbin/vncclient 1', log '/tmp/rdpclient.out', env '', pid ''.
[ pfac] [ 20.465882] Ok, PID 800.
[ vncclient 800] [ 20.491241] VNC Client, WTware 6.2.43/RPi64, pipe 1, pid 800.
[ vncclient 800] [ 20.491414] Use /usr/lib/ui32.so.
[ gm] [ 20.491886] Incorrect "vncclient_keyboard" parameter value.
[ vncclient 800] [ 20.491923] vncclient-main.cpp ( 52): -- ERROR -- INTERNAL ERROR. Please, contact WTware tech support.
[ vncclient 800] [ 20.491982] Oops, something went wrong.
[ vncclient 800] [ 20.492070] Caught signal SIGPIPE.
[ gm] [ 21.096430] Session is over. Final message: Incorrect "vncclient_keyboard" parameter value.
[ pfac] [ 21.096677] Process pid 800 terminated, status 00000009.
Can you do the same for vncclient_keyboard? >>>
[ gm] [ 18.651156] [WTRC] Connection from 172.21.170.243.
[ gm] [ 18.689507] [WTRC] Control password accepted.
[ gm] [ 18.690807] [WTRC] Zoom 75%, 2 bytes per pixel.
[ gm] [ 20.465144] Free ram before fork terminal client /sbin/vncclient (session 1): 7900424 Kb.
[ pfac] [ 20.465346] Run /sbin/vncclient 1.
[ gm] [ 20.465402] Run '/sbin/vncclient 1', log '/tmp/rdpclient.out', env '', pid ''.
[ pfac] [ 20.465882] Ok, PID 800.
[ vncclient 800] [ 20.491241] VNC Client, WTware 6.2.43/RPi64, pipe 1, pid 800.
[ vncclient 800] [ 20.491414] Use /usr/lib/ui32.so.
[ gm] [ 20.491886] Incorrect "vncclient_keyboard" parameter value.
[ vncclient 800] [ 20.491923] vncclient-main.cpp ( 52): -- ERROR -- INTERNAL ERROR. Please, contact WTware tech support.
[ vncclient 800] [ 20.491982] Oops, something went wrong.
[ vncclient 800] [ 20.492070] Caught signal SIGPIPE.
[ gm] [ 21.096430] Session is over. Final message: Incorrect "vncclient_keyboard" parameter value.
[ pfac] [ 21.096677] Process pid 800 terminated, status 00000009.
Re: Language problems in VNC, Terminal login and Chrome #swedish
Do you need any more information regarding the VNC language?
Re: Language problems in VNC, Terminal login and Chrome #swedish
We only have English and Russian in vncclient_keyboard= option now. Why do you think you need vncclient_keyboard=? What exactly goes wrong?
Re: Language problems in VNC, Terminal login and Chrome #swedish
-When i connect to client by vnc (server side is tightvnc and ultravnc, tried both) i cannot type åäö etc.
-When i connect with regular vnc client through my laptop everything works.
This customer only wants to connect with VNC unfortunately. RDP is not an option, although i tried it and it works fine.
-When i connect with regular vnc client through my laptop everything works.
This customer only wants to connect with VNC unfortunately. RDP is not an option, although i tried it and it works fine.
Re: Language problems in VNC, Terminal login and Chrome #swedish
I have also tried Tigervnc on server-side without better results.