- This topic has 6 replies, 3 voices, and was last updated 3 years, 7 months ago by
.
-
Posts
-
The issue: Anytime I type anything in my remote desktop, I get letters that do not correspond to what I typed.
Ex: The key ‘Enter’ becomes a backspace, ‘e’ becomes a ‘9’.
It’s not just on terminal; it’s anytime I need to type. If I login to the remote server using just SSH (no NX involved), everything works fine.
INFORMATION:
NoMachine Product: NoMachine
Version: 7.41
Platform: client (Windows 10), remote: Ubuntu 16.04
Virtual Display (I think)
Using Lightdm on remote
Attached:
(1) xkb.log: result of running: xkbcomp -i 5 -xkb $DISPLAY
(2) xev.log: result of running <em style=”box-sizing: border-box; font-size: 13px; color: #444444; font-family: Verdana; background-color: #e9f8fb;”>xev > xev.log (kept only KeyPress Event)
(3) xmodmap.log: result of running <em style=”box-sizing: border-box; font-size: 13px; color: #444444; font-family: Verdana; background-color: #e9f8fb;”>xmodmap -pkeOnly changes made to server.cfg:
SessionLogLevel 7
PhysicalDesktopAuthorization 0
Output of locale -c charmap:
LC_CTYPE
ANSI_X3.4-1968Hi js,
The log files failed to attach. Please try sending them directly to forum[at]nomachine[dot]com making sure you use the title of the topic in the subject of your email. Thanks!
Hello, xev reports correct events and keymap looks OK as well.
For example, qwerty produces events keypress/keyrelease for Q W E R T Y. I can’t see the E becoming 9.
Enter and Backspace are in the expected place in the keymap.Did you run terminal and Xev in the remote session?
I’m an idiot. I just realized that I couldn’t have run in the remote session because I can’t type anything in the remote session. Even if I copy and paste text into the remote terminal, I can’t figure out which button corresponds to the “Enter” button.
So I finally figured out to run: xev -event keyboard. I typed ‘qwerty’
KeymapNotify event, serial 19, synthetic NO, window 0x0,
keys: 4294967192 0 0 0 0 0 0 0 2 0 0 0 0 0 0 0
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0KeyPress event, serial 22, synthetic NO, window 0x6800001,
root 0x25, subw 0x0, time 1717692215, (-71,-173), root:(352,126),
state 0x0, keycode 24 (keysym 0x37, 7), same_screen YES,
XLookupString gives 1 bytes: (37) “7”
XmbLookupString gives 1 bytes: (37) “7”
XFilterEvent returns: FalseKeyRelease event, serial 22, synthetic NO, window 0x6800001,
root 0x25, subw 0x0, time 1717692367, (-71,-173), root:(352,126),
state 0x0, keycode 24 (keysym 0x37, 7), same_screen YES,
XLookupString gives 1 bytes: (37) “7”
XFilterEvent returns: FalseKeyPress event, serial 22, synthetic NO, window 0x6800001,
root 0x25, subw 0x0, time 1717694967, (-71,-173), root:(352,126),
state 0x0, keycode 25 (keysym 0x38, 8), same_screen YES,
XLookupString gives 1 bytes: (38) “8”
XmbLookupString gives 1 bytes: (38) “8”
XFilterEvent returns: FalseKeyRelease event, serial 22, synthetic NO, window 0x6800001,
root 0x25, subw 0x0, time 1717695110, (-71,-173), root:(352,126),
state 0x0, keycode 25 (keysym 0x38, 8), same_screen YES,
XLookupString gives 1 bytes: (38) “8”
XFilterEvent returns: FalseKeyPress event, serial 22, synthetic NO, window 0x6800001,
root 0x25, subw 0x0, time 1717695315, (-71,-173), root:(352,126),
state 0x0, keycode 26 (keysym 0x39, 9), same_screen YES,
XLookupString gives 1 bytes: (39) “9”
XmbLookupString gives 1 bytes: (39) “9”
XFilterEvent returns: FalseKeyRelease event, serial 22, synthetic NO, window 0x6800001,
root 0x25, subw 0x0, time 1717695429, (-71,-173), root:(352,126),
state 0x0, keycode 26 (keysym 0x39, 9), same_screen YES,
XLookupString gives 1 bytes: (39) “9”
XFilterEvent returns: FalseKeyPress event, serial 22, synthetic NO, window 0x6800001,
root 0x25, subw 0x0, time 1717695549, (-71,-173), root:(352,126),
state 0x0, keycode 27 (keysym 0x2d, minus), same_screen YES,
XLookupString gives 1 bytes: (2d) “-”
XmbLookupString gives 1 bytes: (2d) “-”
XFilterEvent returns: FalseKeyRelease event, serial 22, synthetic NO, window 0x6800001,
root 0x25, subw 0x0, time 1717695681, (-71,-173), root:(352,126),
state 0x0, keycode 27 (keysym 0x2d, minus), same_screen YES,
XLookupString gives 1 bytes: (2d) “-”
XFilterEvent returns: FalseKeyPress event, serial 22, synthetic NO, window 0x6800001,
root 0x25, subw 0x0, time 1717695816, (-71,-173), root:(352,126),
state 0x0, keycode 28 (keysym 0x3d, equal), same_screen YES,
XLookupString gives 1 bytes: (3d) “=”
XmbLookupString gives 1 bytes: (3d) “=”
XFilterEvent returns: FalseKeyRelease event, serial 22, synthetic NO, window 0x6800001,
root 0x25, subw 0x0, time 1717695918, (-71,-173), root:(352,126),
state 0x0, keycode 28 (keysym 0x3d, equal), same_screen YES,
XLookupString gives 1 bytes: (3d) “=”
XFilterEvent returns: FalseKeyPress event, serial 22, synthetic NO, window 0x6800001,
root 0x25, subw 0x0, time 1717696157, (-71,-173), root:(352,126),
state 0x0, keycode 29 (keysym 0x5b, bracketleft), same_screen YES,
XLookupString gives 1 bytes: (5b) “[”
XmbLookupString gives 1 bytes: (5b) “[”
XFilterEvent returns: FalseKeyRelease event, serial 22, synthetic NO, window 0x6800001,
root 0x25, subw 0x0, time 1717696276, (-71,-173), root:(352,126),
state 0x0, keycode 29 (keysym 0x5b, bracketleft), same_screen YES,
XLookupString gives 1 bytes: (5b) “[”
XFilterEvent returns: FalseNew Question: How should I go about debugging this?
Background info: this is my first time using NoMachine. It’s not like I had a working version and some update ruined my settings, etc. I’m using defaults. I checked on the keyboard settings, and it says I’m using system defaults. And when I uncheck the system defaults. I unclicked that and restarted the nxserver, but nothing changed.
This is probably what is going on. I killed vncserver (which I forgot I was running). Now, the problem is that I can’t log in.
After stopping vncserver, and restarting nxserver, I get warning: “Cannot find X servers running on this machine.” Now, when I try to login from the client, a window pops up for about half-a-second, then immediately crashes. That’s all that happens.
To try and get around this, I tried starting lightdm (on Ubuntu 16.04) but I can’t login. What happens is that I when I try to login, I get a “system program problem detected” popup, then I get a screen with nothing but the background (can’t interact with the desktop when it is like this), and then, after a 3-4 seconds, a new login screen is presented.
It is likely a crash in lightdm or in the desktop environment (that is the compiz-based Unity Desktop in Ubuntu 16.04).
If you turn lightdm off, NoMachine will present an option asking you if you want to launch a virtual display server. You’ll get an X11 session although no X server is running on the physical display.
This topic was marked as solved, you can't post.