Forum Replies Created
-
Posts
-
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.
Thank you for the files, they help to narrow possible causes down. Would you be willing now to install a debug package and collect some logs for us?
Hi,
in the meanwhile we reproduced something similar in our labs, but we would need a confirmation. Do you have the possibility to physically look at the server monitor while reproducing the slowness in the NoMachine session? Is the monitor in stand-by mode?
Sorry for the delay. Probably we managed to reproduce this issue in our labs, but we would need a confirmation. Do you have the possibility to physically look at the server monitor while reproducing the slowness in the NoMachine session? Is the monitor in stand-by mode?
Sorry for the delay, still not able to reproduce it here. Anyway your last findings gave some food for thoughts, but we would need a confirmation. Please use the ‘Take a screenshot’ button in the Connection panel of the session menu. Take a screenshot with ‘Show remote cursor pointer’ off and again with this option turned on, and see how many cursors are shown in the image and their size. Then, if you are available to do so, you can use session recording to record the NoMachine session (Recording panel of the session menu). Again, see how many cursors and size. You can share the screenshots and the recording file here, if you wish.
Thank you in advance 🙂
Hi,
we can’t reproduce the issue with black screen in our labs. To start an investigation, we would need server side logs. You can find instructions in https://knowledgebase.nomachine.com/DT11R00182#1 and you can send them to forum[at]nomachine[dot]com. Collect them while reproducing the black screen.
From further descriptions provided by the both of you, it looks like the issue that you are reproducing is not the same we reproduced in our labs (that anyway only affects the initial cursor size, as changing the cursor shape would fix it immediately). So please let us know:
– What happens when you drag the cursor (move the mouse while the left button is pressed)? No matter where you do that, it can be on the desktop. Do you still see two cursors, the huge one and the normal one?
– What happens if you enable the ‘Show remote cursor pointer’ option in the Input menu? Do you still see the same two cursors?
– Could you record a video of your screen showing the problem?