Tor

[Tor]

We still didn’t reproduce the issue, but we’ve found a problem with the backspace key which could be related and we’re investigating it. In the meanwhile you could try to install Simple Keyboard from the Store and switch to it when running NoMachine (even if using the external keyboard): one of our users has experienced a similar issue and has found that such keyboard app helps to work around the unexpected Android 10 kernel behaviour.

[Tor]

Hi. The behaviour is unexpected and we could not reproduce it so far, so I’d be grateful if you can help to debug it.
What is the text editor causing the CPU spikes? Did you notice the same with other remote apps?
It would be great if you can dump some information while the CPU is high, by running the following commands in Terminal:
ps -M $(pgrep nxplayer) > ~/Desktop/threads.log
sample $(pgrep nxplayer) -file ~/Desktop/sample.log (wait 10 seconds for the sampling to complete)
Send the files threads.log and sample.log on your Desktop to forum[at]nomachinec[dot]com.
Thank you!

[Tor]

Hi. Are you using the DeX box or the DeX application? The weird keyboard behaviour occurs also when using the app interface (e.g. when filling the hostname input), or only in the remote desktop? What is the remote desktop OS/Version?

[Tor]

Great! We’ve documented this problem here:

https://www.nomachine.com/TR09Q09412

It is due to X.org not setting correctly the keyboard options for the XTEST extension device. Let’s try to work around it.
Create the file .xinitrc in your home directory (if it doesn’t exist already), and add the following lines (remove the first line if it’s not a new file):

#!/bin/sh
XTEST_ID=$(xinput list | grep -Eo "Virtual core XTEST keyboard\s*id\=[0-9]{1,2}" | cut -d= -f 2)
setxkbmap -device $XTEST_ID -model pc105 -layout it

Run the command chmod +x .xinitrc to set executable permissions and run it to verify that it works as expected. Each time your X session will start, the script will be executed and it’ll set correctly your layout.

[Tor]

If your question still concerns the tray icon, and you mean you don’t see the NoMachine icon on all workspaces of your desktop (in the screenshot I see you’ve two workspaces), then you should investigate the configuration or issues of your environment. The notification area items are initialized only once by an application, then it’s up to the desktop environment to handle it correctly by showing it on all available workspaces.

[Tor]

Hi. Do you mean whether NoMachine can push the resolution beyond the ones supported by Windows 10 notebook? We can’t do that because when connecting to the physical desktop the supported resolutions are those of the remote video card listed in Windows display settings.

[Tor]

Hi Luke. Can you confirm whether the command setxkbmap -model pc105 -layout it executed in the Linux terminal helps to solve the issue?

[Tor]

I’d suggest to enable one tray shell extension at a time to test them, to avoid they interact badly. You can then open the NoMachine client, click Settings and restart the NoMachine server.

[Tor]

I suppose you mean you’re not seeing the tray icon. GNOME 3.x has no drawer showing 3rd party application icons, you can try to install a GNOME Shell extension like

https://extensions.gnome.org/extension/1031/topicons/

or

https://extensions.gnome.org/extension/615/appindicator-support/

[Tor]

Hi Luke. Can you run the command setxkbmap -print in a terminal on Linux and let us know the result? Generally such problems are related to the server keyboard layout not matching the physical keyboard you’re using on the client. For example if you’re using an italian keyboard on Windows, select the italian layout on the server so the remote system correctly interprets the pressed keys.

[Tor]

They are disabled/non-functional, but not hidden as before.

Hello mw32. I’ve quoted the text above because as far as I understand it is what you’re seeing now, please tell me if I’m wrong. Menu controls are just disabled to prevent users from accessing them and keep the menu bar consistent (a menu bar with just one or two items would be terrible! 🙂 ). As far as I remember we’ve never hidden them and I didn’t find documented issues about this behaviour.

[Tor]

Thank you Matt, we’ll keep an eye out for this problem. If you’ll reproduce it again, don’t hesitate to contact us.

[Tor]

2. mouse and keyboard will work initially for a few minutes. Then when you try to use either input device terminals start closing and then the connection closes

The terminals closure could be caused by this issue:

https://www.nomachine.com/TR06R09781

When you notice input starts working badly, try the workaround described in the Trouble Report. I’d be grateful if you can confirm it.

[Tor]

After the last upgrade I started seeing this same issue. Linux terminals just hang and won’t accept any inputs.

If you’ve the same issue reported by Matt (menu opening, etc), could you answer to questions 2, 3 and 4 of my previous post?
Additionally, do you’ve issues only with terminals or with any application running remotely?

[Tor]

Yes, correct.

https://www.nomachine.com/getting-started-with-nomachine-for-android

[Author]

Posts