Forum Replies Created
-
Posts
-
The logs don’t seem to contain any problem related to starting virtual sessions. Can you make sure you follow the steps here: https://www.nomachine.com/AR07K00677 in the section dedicated to Linux.
You will need to:
1) Set log level to debug as per instructions
2) Reproduce the problem.
3) Create a compressed archive of the NoMachine /var/log directory.
4) Send the archive to NoMachine Support Team by e-mail .
Don’t forget to include the client side logs as well. The userhome/.xsession-errors file will be useful to. Send everything to issues[at]nomachine.com.Hi snejok, from this post:
Under “more quality of image” I mean fonts blurring (https://www.nomachine.com/forums/forums/topic/blurry-fonts-with-latest-nomachine-viewer)
you will see that we are working on improving text rendering.
option key=”Link speed” value=”wan” is a legacy setting and only takes effect when connecting to a 3.5 server. If you are connecting to a server 4, the setting option key=”Link quality” value=”7″ is used. Changing it to 9 (this corresponds to the slider being on the far right in Display settings) will give better image quality, but will also require more bandwidth.
As Fra81 explained in his reply to the topic quoted above,
“The slider can be changed according to the quality of image that you prefer. By default it is set in the middle. Moving it to the right edge will activate lossless encoding. This should make fonts sharper….Additionally, you can also check the box ‘Disable multi pass encoding’ to avoid progressive refinement of the screen image. Disabling this refinement sends the image directly with the target quality (set in the slider).”
We haven’t been able to reproduce this error. Are you able to send us logs?
https://www.nomachine.com/AR07K00677
You attach them here, or send them to issues[at]nomachine.com making sure you include your topic title in the subject.
Did you try to change the port in the panel I have attached here?
Attachments:
There is no way to disable this certificate warning, it’s a security feature.
Show SSL certificate storage warning
This key is used to disable a warning issued when the key cannot be saved on disk.
The problems with the keys improved quite a lot by updating to the latest version of NX on both PCs.
When you say that there are improvements, do you mean that problems with keys being repeated or not received has gone away completely, or are there still issues?
If I left the connection idle, the screen went black after a couple of seconds. I disabled the power saving screen blanking (its timeout was set to 10 minutes. With that change, the blanking issue has gone away.
We’ll look into this.
Can you send the logs to issues[at]nomachine.com please? Make sure you provide the info I requested in my earlier post.
Thanks.
For a detailed explanation on these directories, please see the following article: https://www.nomachine.com/AR12K00765
In brief, the C-hostname-display-sessionID directories are for managing the connection to the physical desktop or virtual desktop. You will probably have also seen S-hostname-display-sessionID directories; these are related to the client monitor run for each connection.
When you terminate a session, NoMachine’s default behaviour is to delete all old directories from your .nx on the server side unless NoMachine is configured to preserve them, e.g. for debug purposes. When you disconnect your virtual desktop, a C-* and the S-* directory is left in your .nx to be ready for the reconnection.
A correctly terminated session is renamed to T-C-*. When you find a F-C* or a F-S* directory in your .nx , it means that something went wrong and the session or the client monitor has been terminated unexpectedly or incorrectly. You can safely remove all T-C*-*, F-C-* and F-S-* directories.
Be careful not to delete a C-* or a S-* directory as it will cause the sudden termination of the current connection.
To ensure that NoMachine deletes all old directories, edit the node configuration file, namely node.cfg, uncomment and set the SessionLogClean key to:
SessionLogClean 1
Did you update the client side software to version 4 as suggested? If so, we will need to see logs from both sides, plus the information that is listed in ‘What to include’ just below. Note that we’ve since release 4.0.369 and you can use the automatic updates to get the latest fixes.
To update your installation:
– Run the NoMachine GUI from your Programs menu.
– Access the ‘Change server settings’ panel.
– Click on the ‘Software updates’ button (last little icon on right).
– Click ‘Check updates’.
If the logs are too big, send them to issues[at]nomachine.com referencing your topic.
Thanks.
Hi,
We are not away of any bugs. Are you able to provide some more information?
– Do you have a multi-monitor setup on the Mac server?
– What is the version of your Mac server?
– Is the “Keep original aspect” button selected in the Display settings panel?
What behaviour do you observe when switching it?– What part of the remote screen are you able to see? The one with the upper left corner?
– Are you able to navigate the viewport by moving the cursor near the border of the player
window? Can you see in this way parts of the remote screen that were previously hidden?– Is the problem fixed if you change the resolution of your Mac screen by means of the
“System Preferences -> Displays” pane and restore it back to the previous value? (see screenshot)Attachments:
See this post Sanki
https://www.nomachine.com/forums/forums/topic/thin-client-with-4-or-more-monitors
I think what you need is the functionality documented in the Feature Request here: https://www.nomachine.com/FR11K02797
The steps to generate the cookie are:
1) $ COOKIE=
ps -ef | md5sum | cut -f 1 -d " "2) $ sudo xauth -f /var/run/Xvfb-0.auth add :0 MIT-MAGIC-COOKIE-1 $COOKIE
3) $ xauth add :0 MIT-MAGIC-COOKIE-1 $COOKIE
We’ll update the article 😉
Check that you have set up your forwarding to port 4000. If you are connecting via NX, NXD listens on the default port 4000.
Bug confirmed. A Trouble Report is open (https://www.nomachine.com/TR12K04131). We’ve added a notification facility to all TRs now, so you can receive an email when the fix has been released.
