graywolf

[graywolf]

I think the Ctrl+Shift combo is intercepted by Ubuntu desktop.

[graywolf]

Sorry, I don’t understand: did you upgrade NoMachine or Ubuntu?

So, which version of NoMachine are you using on client and server?

[graywolf]

Hello. It is not clear to me if that occurred after the upgrade of Ubuntu or NoMachine.

Would you tell me which Ctrl+Shift combination doesn’t work to you? Which action is associated with?
Do you expect that keyboard shortcut doing some action in the server-side Windows desktop or in the client-side Ubuntu one?
Would you try if changing setting “Grab the keyboard input” has any effect on such issue?

[graywolf]

Hello. The screen nxoutput0 is in virtual NoMachine sessions. So the remote access is not using an existing Xorg display. It looks like the Xorg display on your server failed for misconfiguration. “Number of created screens does not match number of detected devices” means that you have too many Device sections in you xorg.conf. I would rename existing xorg.conf and xorg.conf.d/* into backup files then retry to configure Xorg from scratch.

[graywolf]

Hello.
Does it occur all the times? As Trouble Report already exist, but requires some conditions being matched: NumLock and CapsLock status is not preserved on Windows when it’s changed while the NoMachine window is minimized

In case the problem you are facing is different, would you provide any piece of information useful for us to reproduce it?

[graywolf]

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.

[graywolf]

Hello. Here’s the TR: Right mouse button behaves like left button if Control key is pressed down

[graywolf]

Hello, the log actually shows 10 events Ctrl+LeftClick where you issued 5 left and 5 right button clicks. It looks that events are created with wrong button code. We managed to reproduce, so I think we are going to open a Trouble Report.

[graywolf]

Do you manage to run a terminal in the remote session and type the command setxkbmap fr ? Does it change something?

[graywolf]

Xvnc has such a keymap. Is it possible you are running Xvnc in place of Xorg?

[graywolf]

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?

[graywolf]

Hello. I would expect to find ButtonPress/ButtonRelease events, but I can’t see any.
I had to spend some more words about the way xev works, sorry. In order to record events, you have to generate them on the xev window: move the pointer over the xev window, then Ctrl+click on it.

[graywolf]

I don’t know if it is possible to setup Xorg to be fully functional with lid closed. Let me suggest to compare the Xorg log in the two cases: started with lid closed and with lid open.

[graywolf]

Hello.

Does it makes any different if you use a different client machine with a different OS, Windows for example?

Inspect events forwarded on actions Ctrl+Left Button and Ctrl+Right Button. Launch the xev tool using a terminal in the remote session. You would restrict inspection to mouse and keyboard events for better readability: xev -event keyboard -event mouse

[graywolf]

Black Xorg screen make me think KDE failed to find connected physical screens. Let me suggest to look at KDE log as first thing (try: journalctl -b -0 | grep -i -E "kde|plasma"). Then look at NoMachine logs (specially search for files $HOME/.nx/*/session).

[Author]

Posts