Forum Replies Created
-
Posts
-
I’m not sure what you meant in the third item.
I meant on the Windows machine you are connecting from. Do you have a custom desktop scaling set to maybe 125%, for example?
Server side logs show nothing strange (Kath) and the client side logs are still empty.
On the machine Sophie, please open the Player, go to Player settings and tick the checkbox “Don’t delete log files…:” Then go back to the Machines tab in the Player on Sophie and start your connection to Kath. Do not close it, but keep the Player open. Then, create a compressed archive of the .nx directory (whilst the Player window is still open, you might be seeing the wheel spin like you described)
sudo tar -cvp --exclude 'cache*' --exclude 'images' --exclude 'temp' -f - PATHTOUSERHOME/.nx | gzip -c nxdir.tar.gzPlease check the following:
– if scaling mode is enabled in the Player, try to disable it.
– enable ‘Show remote cursor’ and check whether the remote cursor’s shape changes or not
– is desktop scaling set in the OS settings of the Windows machine perhaps?No logs were received. For this reason the topic is now closed. Please open a new topic if you continue to encounter the same issue, but without logs we will not be able to investigate.
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.