Forum Replies Created
-
Posts
-
Hi, this is still under development. Please sign up to receive notification of when it has been implemented (‘notify me’).
You can share a link with us to a file-sharing service – send the link to us privately via forum[at]nomachine[com] and we’ll download it.
Or are you actually still using that version (custom 6.8.1) we sent you? It is that package which contains the fix, and at the time, when you tried it, you said it was much better.
I updated the closed topic because I wrote the patch had been released, when in fact it hasn’t. Sorry if that was misleading.
The package link is still available if want to go back to using that version.
The TR has just been updated. Apologies for the confusion.
I confirm that screen blanking doesn’t work when remoting in to a Win 10 (update 1909) with two or more monitors.
Enterprise Desktop simply shows you the physical display of the remote system, so you’ll need to set up the remote system to have two monitors. To do that, you could try following the suggestion here: https://unix.stackexchange.com/questions/378373/add-virtual-output-to-xorg and see if that helps.
If you were using Workstation (from the Terminal Server family which supports multiple virtual Linux desktops), with the implementation of this Feature Request, https://www.nomachine.com/FR10N03220, you will be able to treat those multiple monitors on the server side as separate windows on the client side. This feature is in its final stages at the moment and will be released in a future update.
Do you still want log files from me?
Yes, submit them so we can check whether the problem is the same one as JimH24’s 🙂
Ryan, we received the logs but you didn’t send us the logs from the server side – the remote computer. Also, what you sent us seems to be just the installation dir from the client side, it doesn’t contain the user home directory which is what we need to see.
For the Windows client: write the following in the address bar or the file browser:
USERPROFILE\.nxor navigate through the computer folder till the user’s home and type .nx in the navigation toolbar to reach the folder. The path can be similar to: C:/Users/USERPROFILE/.nx
Zip up this folder.On the remote Windows host, zip up NoMachine’s /var/log folder typically found at PROGRAMDATA/NoMachine/var/log.
Hi, what desktop environment is running on Centos in both the 6 and 7 installations?
Do you have a monitor attached?
We are investigating a specific issue related to the dual monitor set ups.
The TR I referenced above was specifically for single monitor set ups and we have verified that it by updating Windows to the lastest (1909) the issue disappears, so we have closed it.
Hi ryan,
thanks for the image.
Can you submit logs from both client side and server side?
Instructions on how to to do that are here:
Server side – https://www.nomachine.com/DT10O00163#1.4
Client side – https://www.nomachine.com/DT10O00163#2.3
Send via email to forum[at]nomachine[dot]com making sure you reference your topic 🙂
That’s a useful idea 🙂
We’ve opened a Feature Request (under review in the meantime).
Add an option to disable copy-on-select
https://www.nomachine.com/FR01R03924The default is set to ‘0’. If you wanted to change it and set it to ‘1’ (but I doubt it would change anything because this key was inserted to mitigate a problem coming from old packages), then you would need to remove the #.
@JimH24, the logs you sent didn’t show anything strange. Do this instead: from inside the NoMachine session, open a terminal and execute this command:xev -event keyboardthen press the not working keys and copy the output you get in the terminal. Paste it here or submit a screenshot.