Forum Replies Created
-
Posts
-
Hi, we have managed to reproduce a similar problem and it was triggered by the OS’s display scaling to 125%. The workaround in our case was to switch back to 100%. Could you make sure that your Windows display is configured to scale at 100%?
Hi,
thanks for updating your topic. I’m glad to know you fixed the issue. From what you described you have a headless Linux. We have an article in our knowledge base which provides guidelines for Connecting to Linux headless machines with NoMachine such as disabling the Xserver. You can find it here: https://knowledgebase.nomachine.com/AR03P00973. If NoMachine detects that the X server is already running, it doesn’t use its own virtual display and that is what triggers the “no available desktops” message.We have a fix for a similar problem included in the next maintenance release which has been scheduled for next week. Looking at the errors you pasted, it is possible that this could solve your problem with Cadence. I would wait to try that first.
Hi,
I wrongly assumed you had installed the free version on the remote host you are accessing hence the suggestion to install Workstation or another product from the Terminal Server range. You didn’t need to uninstall NoMachine Workstation and then install Terminal Server, so sorry for the confusion. They both support HW acceleration in NM virtual desktop sessions provided you enable VirtualGL on the server where you have installed Workstation/Terminal Server. We checked that the extension that you highlight as important is present in VirtualGL.
Please verify that you do have VirtualGL installed and that is enabled. Prequisites are that the host machine is a physical computer and has a hardware-accelerated 3D video card, and that Xorg is up and running to use the 3D video card.
You can follow the instructions here to enable VirtualGL:
How to enable VirtualGL support on Linux in NoMachine v. 6.2 or later
https://knowledgebase.nomachine.com/AR05P00982We have reproduced this behaviour and opened a Trouble Report which you can monitor at this link:
https://knowledgebase.nomachine.com/TR03T10493
A temporary workaround is to install Zenity or Kdialog in order to browse the file system.
Our sysadmin are on it 😉
If you need information, feel free to post a new topic on the forums. Or you can write directly to info[at]nomachine[at]com if you prefer (normally you would do this via the website on the Contact Us page, but given that it is not accessible…)
Hi, Forums and the Knowledge Base are accessible. The store and main website are temporarily offline for maintenance. If I can be of help here, let me know 🙂
Hi, can you submit the image again as a separate attachment? or send it to forum[at]nomachine[dot]com and I will upload it to your original topic. Thanks!
We aren’t aware of any issues of installing NoMachine in a VM provided the VM is running on Mac hardware. Is this your case?
macOS’s EULA doesn’t allow macOS to be installed in a VM that is not running on Mac hardware as far as I am aware. Due to these licensing restrictions it’s not possible for us to investigate installing NoMachine in VMs which are not running on Mac hardware.
After installing ‘zenity’ the update works as described. (your RPM does not mention it in its requires list)
Zenity is not a requirement for installing NoMachine hence we don’t write that is required. If it’s present on the system we use it, if it’s not present NoMachine opens the dialog to enter the password.
What NoMachine product and version have you installed on the local side and on the remote side?
I need to know the above information so that we can understand your set-up better.
With NoMachine are you remotely connecting to the physical desktop on Windows, are you connecting to a Linux desktop? Does the middle button stop working only when you connect to the remote desktop with NoMachine?
What OS are you connecting from? What OS are you connecting to? and version?
What NoMachine product and version have you installed on the local side and on the remote side?
Was the middle mouse working in a NoMachine remote desktop session before? What might have changed, if anything, since it was last working? An update?
invanvi, it could be related to HW decoding.
Can you disable HW decoding on the client side and tell us if this changes anything? Start the session, open the connection menu Ctrl-Alt-0, Display Settings -> Advanced (click modify) and check the box “Disable client side hardware decoding”.
You can also try disabling “client-side image post-processing”.
What happens?