Forum Replies Created
-
Posts
-
Hi.
I can see it move over the login screen, but I can’t click in anywhere.
Do you mean that you can see the cursor moving on the actual MacBook’s display, when looking at it locally?
Can you try to disable and re-enable privacy permissions for ‘NoMachine’ and ‘nxnode’ in Security & Privacy -> Accessibility.
Does the issue persist if you reboot the MacBook?
Hi,
assuming you’re running a NoMachine virtual desktop, you can enable VirtualGL support. Please check this article:
Hi,
we got this problem before. We investigated and excluded it was a NoMachine issue, but it was rather an issue related to the RANDR X server extension. No Trouble Report exists for this problem and that was a mistake. This issue is annoying and a TR would have been useful as a reference for anyone reproducing it. When the lag occurs, do you experience the same lag on the local, physical machine?
From the investigations we found that applying a resize of the screen of the desktop, using the RANDR X extension, resolved the problem. I don’t remember if applying a resize with the same size the desktop already had made the trick, but you can try it yourself. To try this, open a terminal and use the xrandr command to list the available resolutions (‘xrandr -q’), then set one of them (‘xrandr -s WxH’). This should clear the lag. Another thing we could do is sending a fake input event at intervals to prevent the screen from going to sleep, but this can be obviously annoying, for the user, that would never get its screen into sleep.
BTW, are you using an NVidia graphic card? Are you using the NVidia proprietary graphic driver? Because also these two X driver’s bugs can apply:
https://askubuntu.com/questions/1053973/mouse-cursor-lags-behind-after-screen-lock-user-switching
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1757202
Hi,
do you have the possibility to try to connect from a different client (either Windows, Mac or Linux), just to narrow it down and make sure it is a problem only with the iPad?
Please also tell us about your iPad model and iOS version.
Sorry for the delay.
When the MacBook’s lid is closed, normally you shouldn’t even be able to connect at all. Unfortunately this is prevented by the system, unless you use an external app that prevents system sleep, plug a fake display adapter or keep an active ssh connection to the MackBook. Also the NoMachine built-in Wake-on-LAN feature may help, depending on system and network configuration. If I understand, you seem to be able to connect, but you get a black screen. Are you using any of those methods to keep the machine awake? Are you still using the Beta version of Monterey?
Hi,
your setup isn’t clear to me. NoMachine free is for connecting to the physical display, so how is a ‘virtual desktop’ involved? And how are you using VGLRun exactly?
Hi,
that effect is due to the RGB-to-YUV colorspace conversion needed for image encoding. There are also lossless encoding methods available in NoMachine that do not show this effect. To enable them, please see how to set the “pack” option in the ProxyExtraOptions key in the relevant section of this article: https://knowledgebase.nomachine.com/AR06Q01034.
Alternatively, you can disable the ‘X11 vector graphics mode’ in the Server settings -> Performance tab. This will enable the ‘lossless refinement’ feature, that will progressively refine images to get rid of the effect of color subsampling, by still being very effective on the bitrate.
Hi,
this is not a known issue. Please gather the NoMachine logs as explained in https://knowledgebase.nomachine.com/AR10K00697. You can send them to forum@nomachine.com, by referencing the link to your post.
that the client is still connected and further connections are impossible
This should not be happening at all. I don’t think the problem is about closing the client window, because this is the normal way to disconnect a session. In order to check what is actually the problem, you can gather the logs from the server as explained in https://knowledgebase.nomachine.com/AR10K00697 and send them to forum[at]nomachine.com.
Even if you are connecting to a virtual machine, NoMachine is still connecting to the “physical” display of that machine. The fact the hardware is virtualized doesn’t change the bottom line: if the machine is configured to have one monitor, the applications running there will “see” that one monitor.
I have this downloaded on both systems https://www.nomachine.com/download/download&id=5 which I believe is part of the product line you’re talking about, correct?
The product line I’m talking about is not free but it is available for evaluation. See for example the Workstation: https://www.nomachine.com/download/linux&id=13. This product enables the possibility to create a virtual display (virtual desktop), that can have any number of virtual monitors.
We reproduced the issue in our labs and it will be fixed in the next release. Thanks for reporting!
You probably mean this feature: https://knowledgebase.nomachine.com/FR12K02799. This is already implemented, but only in virtual desktops, that are available in the NoMachine Terminal Server product line (e.g. NoMachine Workstation). When connecting to a physical desktop, you are limited by the number of monitors actually present on the server.
It’s a bit strange that disabling the pointer grab can have an effect on this issue. Would you double check?
Please also try to check the ‘Show remote cursor pointer’ option. Now you should see two cursors in the session, the local one and the remote one. Do they both look large or just one of them? Which one?
Hi Mark,
server side logs look clean, so I would need some more information. Is the Linux machine on the login screen when you connect to it? Is it headless (no monitor attached or turned off)? In case it is headless, can you try to attach a monitor and check?
Hi mjordam,
at that stage the OS is asking all applications to terminate now, including NoMachine. It looks like some other application is misbehaving here, not NoMachine. I don’t know if any trick would be possible to allow NoMachine wait for all other applications, but I’m afraid it wouldn’t feel right.