Forum Replies Created
Now it’s clear. X display launched by TightVNC has its own keyboard map. Moreover, it lacks the KEYBOARD extension (XKB), so setxkbmap and xkbcomp cannot work.
If you change that keymap you could make it compatible with NoMachine, but likely you’ll mess up the keyboard for VNC client.
If you want to go on anyway, you have to use xmodmap to edit the map, as XKB is not available.
You could gather a more usual keymap from a different X display (non VNC):
xmodmap -pke > xmodmap_ok.txt
then connect through NoMachine to the VNC X display and load the map with the command:
xmodmap xmodmap_ok.txtApril 6, 2020 at 13:53 in reply to: NoMachine – Users cannot reconnect a virtual desktop session at the last port #26561
Didn’t it help with recovering the session or didn’t shadowing even work?
Anyway, would you send server and client logs, if possible?April 6, 2020 at 09:16 in reply to: Konsole does not appear to update the display on every keyboard/mouse input (2) #26539
Does xinput produce any output?
Could you send the server session log located at /usr/NX/var/log/node/C-…?
Is the problem reproduced with non-KDE applications (xterm, for example)?April 3, 2020 at 17:50 in reply to: Cannot open session: WARNING! Failed to open display ‘:1024’ #26510
It fails at an early stage. Is any monitor attached to the video output of the server? Or is it run headless?
I don’t know how a such keymap is loaded in the Ubuntu server. Would you run a few other commands in the remote session, in the same way:
xmodmap -pke > xmodmap.txt
xkbcomp -xkb $DISPLAY - > xkbcomp.txt
xprop -root | grep XKB > xprop.txt
setxkbmap -print > setxkbmap.txt
Would you test the keys Q,W,E in the remote session with the xev tool (keyboard is not working but you could copy and paste the command included the newline):
xev -event keyboard
Take a look of Input preference in the NoMachine Player settings: you can change shortcuts definitions included Ctrl+Alt+T.
For WinKey, you need to start the remote session, invoke the NoMachine menu with Ctrl+Alt+0, select Input tab and check “Grab the keyboard input”.
There is no plan to make it optional. Would you tell me why do you need to disable it? How does it impact on your workflow?
I see this:
_XKB_RULES_NAMES(STRING) = "/usr/share/X11/xkb/rules/evdev", "pc105", "us,pl,us", ",,", ""
I think the problem would go away if the rules part were set to “evdev”. Please try to run this command in the remote session:
setxkbmap -rules evdev -model evdev -layout us,pl,us
disconnect and reconnect.March 31, 2020 at 15:42 in reply to: Cannot open session: WARNING! Failed to open display ‘:1024’ #26393
May I ask you to reproduce using a debug library, gathering server logs and send to forum (at) nomachine (dot) com ?
Glad to know you sorted it out. About Alt+Wheel, I’m afraid there isn’t any way to disable it, sorry.March 31, 2020 at 11:32 in reply to: Cannot open session: WARNING! Failed to open display ‘:1024’ #26368
Hello. Is that a virtual machine? Or is the NVIDIA proprietary driver installed?
Please, would you send the results of commands (in remote session):
xprop -root | grep XKB
xinput listMarch 31, 2020 at 11:18 in reply to: NoMachine – Users cannot reconnect a virtual desktop session at the last port #26366
Sorry, my fault. The right combo is Ctrl+Alt+DoubleClick.
Alt+mouse wheel provides horizontal scrolling, indeed. It’s helpful with devices lacking horizontal wheel.