Britgirl

[Britgirl]

No unless you enable VirtualGL. Check this article to know how to do that:

https://kb.nomachine.com/AR05P00982

With VirtualGL the rendering is done using the GPU. You will need a product from the Terminal Server Family to use VirtualGL.

[Britgirl]

Hi netmind,

try the following:

– Right-click the NoMachine User Interface (NoMachine app) shortcut on your desktop and select Properties
– Select the Compatibility tab
– Click “Change high DPI settings”
– Check the box “Override high DPI scaling behavior”
– Select “Application” from the combo under “Scaling performed by”

[Britgirl]

We’ve opened a Trouble Report for this issue. Please use the following URL to track its status

Hardware keyboard doesn’t work correctly on iPad
https://kb.nomachine.com/TR04U10847

[Britgirl]

Check your inbox Timo.

[Britgirl]

for DRVNAME in $(find /usr/lib -name "*drv_video.so" -exec basename {} \; | sed 's/_drv_video.so//'); do for DEVICE in /dev/dri/* ; do LIBVA_DRIVER_NAME=$DRVNAME vainfo --display drm --device $DEVICE 1>/dev/null 2>/dev/null ; [ $? -eq 0 ] && echo "$DRVNAME $DEVICE" ; done ; done 2>/dev/null | grep -v dummy

 

did you run as I have pasted above? We noticed that in your output shows -display drm -device... and not --display drm --device... (my fault maybe because I didn’t put my text in tags, since corrected)

If that does not produce any output, you can try with “find /usr/lib64......” instead of “find /usr/lib.....”

Provided there is some output you should then

1. edit /usr/NX/bin/nxplayer
2. add line

LIBVA_DRIVER_NAME=name

where ‘name’ is the driver that shows in the output. This instructs va-api decoder to use that specific driver. You should place it before the line:

exec "$NX_SYSTEM/bin/nxplayer.bin" "$@"`

3. Then start your NoMachine session. If it does not work, the ~/.nx/R-*/session directory will contain more info.

[Britgirl]

Ilgaz, we would need the output of vainfo --display drm', because nomachine specifically uses ‘drm’, not the ‘x11’

Here’s a one-liner for bash that should print only drivers and devices that will work (if nothing is printed, then nothing works). It iterates through all devices in /dev/dri and all drivers in /usr/lib/*_drv_video.so:

for DRVNAME in $(find /usr/lib -name "*drv_video.so" -exec basename {} \; | sed 's/_drv_video.so//'); do for DEVICE in /dev/dri/* ; do LIBVA_DRIVER_NAME=$DRVNAME vainfo --display drm --device $DEVICE 1>/dev/null 2>/dev/null ; [ $? -eq 0 ] && echo "$DRVNAME $DEVICE" ; done ; done 2>/dev/null | grep -v dummy

[Britgirl]

Are you able to test with a different mouse? Does that work without issues?

It would be useful to see the xev output. Start the ‘xev’ utility on the Ubuntu machine and show us the output when you reproduce the problem with the mouse.

[Britgirl]

We’ve reproduced this. It is unrelated to AWS can be reproduced on any headless. As a workaround you can use NoMachine’s resolution slider in the connection menu instead of the system’s own settings to change the resolution.

[Britgirl]

Thanks for your comments and feedback 🙂

The TR you mentioned is something different.

Our app design consists in multiple processes handling the Dock integration and the remote desktop windows presentation, and there are some “minor inconveniences” like determining the previous application activation when NSWorkspace reports a hiding event. We’re investigating for ways to improve this behaviour.

[Britgirl]

Does this article help you?

How to set up key based authentication with NX protocol
https://kb.nomachine.com/AR02L00785

[Britgirl]

Hi, we got your nxd attachment and the recordings, thank you.

We would also need server- and client-side logs. Please follow the instructions you can find here and send them in the same way as you did your nxd log 🙂 https://kb.nomachine.com/DT07S00243

Could you also tell us if the mouse offset is getting bigger when you move it to the bottom right corner of the screen (with show remote cursor enabled).

Thanks.

[Britgirl]

“I was using the VM for over a year with out an issue”.

Is there anything you perhaps installed/updated before the problem occurred? Ubuntu updates, new drivers, etc ?

The ~/.xsession-errors log would also be useful.

[Britgirl]

You didn’t submit the logs that you mentioned.

I would uninstall, remove all traces of NoMachine, and then reinstall the latest packages (now 8.5). If the problem is still there, please provide:

– Linux distribution server side

– desktop environment server side

– client OS and version

and logs from both sides. The instructions for gathering logs are available here:  https://kb.nomachine.com/DT07S00243.

[Britgirl]

Attached find the .nx folders _old is the one I had fore some time, the other one is from today after restarting nxplayer.

 

There are no logs there. This is because the logs are automatically deleted when you close the session. Since it is not possible to tick the box “Don’t delete the log files on exit” in the Player settings (given that you can’t see the check box 🙂 ), what you should is launch the session and get the logs whilst the session is still running. Thanks!

[Britgirl]

Hi, this topic is going to be closed.

NoMachine Free Edition does indeed work as both client and server. You can shut down the server on the computer you are connecting from if you wish. Alternatively, we also offer Enterprise Client which does not include the server component at all.

If you’re having problems with file transfer, can you please open a new topic? Thanks 🙂

[Author]

Posts