Forum Replies Created
-
Posts
-
No further information was received so this topic is now closed. Please open a new topic if the issue continues and we will start a new investigation.
It should be working out of the box. Logs from the server would be useful. Please check the instructions here and submit to forum[at]nomachine[dot]com.
Logs show that the error seems to be in the GPU pipeline and with nouveau.
Please try disabling GPU rendering. You can do this by setting the following option key
"Enable GPU rendering" value="true"tofalsein player.cfg.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.
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”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/TR04U10847for 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 dummydid 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 lineLIBVA_DRIVER_NAME=namewhere ‘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-*/sessiondirectory will contain more info.Ilgaz, we would need the output of v
ainfo --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 dummyAre 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.
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.
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.
Does this article help you?
How to set up key based authentication with NX protocol
https://kb.nomachine.com/AR02L00785Hi, 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.