Forum Replies Created
-
Posts
-
We’re going to send you a client side package which includes a patch. We’d like you to install this client version and use it to connect as you normally do. Tell us the outcome when connecting.
We tested again with i3-gaps and everything is running fine. Please try with the free x84_64.tar.gz package and tell us if you still get the same behaviour.
I guess I don’t have high hopes seeing that it was created in 2015
Work is actually being completed on this right now.
Hi, thanks for this additional information, this is really useful and the developers are looking further into this. In the meantime, I’m going to send you a private email to the link to the library along with instructions. Once you’ve installed it, you’ll to reproduce the problem and then submit the logs again.
Hi MickM, the problem is that despite dedicating considerable time to this topic, the bug and trying to reproduce it in our labs, our developers have been unable to do so. Not even with Cadence or similar apps which we have in our labs and which we test regularly with. So no progress has been made in identifying what is causing it since we haven’t been able to duplicate this very weird behaviour. From the logs we can see an excessive number of requests from Cadence and we know from your earlier observation this doesn’t occur in a virtual desktop session, only in custom session. (My suggestion here would be to use a virtual desktop session rather than a custom session in the meantime, if you can, to avoid the redraw issue).
The specific steps is what we need in order to reproduce the behaviour, as Graywolf suggested. This is the only way to go forward with the investigation and the forums is not the place to do this.
So, I know that you are connecting to a Workstation and that the server is perhaps not managed by you, but by an administrator (?). In that case, what I advise you to do is open a support enquiry if it is not running as expired. This will allow us to correspond more freely without having to worry about sensitive information being made public. Alternatively, you can submit a “report issue” (support page of website, scroll down to he bottom) and we take it from there. Bear in mind, however, that we will need the version of Cadence, we will need the precise steps to reproduce the error in Cadence and a possible plain test case for us to use. Additionally, and if necessary, we can reach out to Cadence since we also have a direct channel with them as well.
I’ll leave the topic open for a while to allow you to reply if you wish to, after which I’ll close it and alert the team to this thread in case you decide to reach out to us via the website.
We make regular tests on Arch (rolling release) so this is strange.
Can you tell me what the kernel version is and system architecture?
Also, what desktop environment are you using?
This is a known issue and there is a temporary workaround.
White screen occurs when macOS is rebooted just after the installation of NoMachine
https://www.nomachine.com/TR06R09746If you want, I can send you a patched version for you to try.
Very strange.
Would you be willing to run a debug library so we can get some detailed logs from the affected Mac server?
Having “Disable client side hardware acceleration” checked when I connect doesn’t work either, then I have to click the check box twice for the image to appear.
We need to verify that you are referring to the”Disable client side decoding” box in the menu. Do you have to click the check box twice because the little tick doesn’t appear the first time at all?
Windows 10 PC that doesn’t have password so I let the password box empty
When NoMachine prompts you to insert the username and password, you need to insert the credentials of the account of the Windows machine. Remote login to Windows with empty password is forbidden by Windows policies. Please refer to this article in our knowledge base: https://www.nomachine.com/AR05L00802.
Sorry, my mistake. I was mixing up two different topics. The fact you have to disable hardware decoding on the client side indicates a different issue. I’ll update this topic when I have some news from the developers. For now, please continue to use the workaround that fits your case.