Tor

[Tor]

Hi. I’m sorry for the slow answer, we were checking your reports.

Issue 1

We’ve identified the problem and implemented a fix, it’ll be released shortly. You can track the fix here:
https://www.nomachine.com/TR10Q09458

Related issue with a slightly modified workflow

This is a little bit more tricky. The problem is related to our fullscreen mode, which is not making use of Spaces and gets confused by a particular sequence of events, causing the menu bar to be visible. There is not an easy fix for this unluckily. Our development branch uses a correct fullscreen mode, but that patch is bound to some other changes that are not ready to be released in a short time. The only workaround consists in swipe-switching to the current NoMachine Space before clicking the Dock icon, or switching the Space when the menu bar is visible to hide it.

[Tor]

Hi. If you want to start the NoMachine client you should execute /usr/NX/bin/nxplayer from a terminal, or just use the NoMachine entry in applications menu. The nxclient application is not meant to be started manually, it needs the communication with other NoMachine processes in order to work correctly. The binary name didn’t change for historical reasons. 🙂

[Tor]

Same problem here. I can’t see my old saved connections in NoMachine client on upgraded macOS Catalina. Also when adding a new connection it’s not possible to add a private key. After selecting path to private key file the filed stays empty.

Hi taras. When running on Catalina the client will ask you when it wants to access your Desktop or Documents folders. If you don’t grant that permission you can still do it at a later time: open Settings, Security & Privacy, Privacy group, select Full Disk Access permission, press the ‘+’ button and select NoMachine in the list of applications.

As for the private key, we’ve found a problem with file browsing and we’re working on it with high priority, I’ll update you soon about the status. In the meanwhile you can edit the NXS file to manually add the private key file path in this field:

<option key="Private key" value="" />

[Tor]

Hi. Your monitors are 5120 x 1400 at full size, so in order to avoid scrollbars you should either enter fullscreen mode, or set a custom size matching the size of your window maximized (more or less that 5119 × 1368 of the old post). You could also enable “Resize remote screen” and enter fullscreen: in that way you don’t even need to set the custom resolution because the client will automatically use 5120 x 1400.

[Tor]

Hi. Swipe left the server item, tap the Edit icon, verify that in the Host field the selected address is the correct one. If you’re not sure, try all addresses you see in the list.

[Tor]

Hi! Old servers discovered in LAN could stay in the cache for a few hours before being completely removed, so just wait a little bit. If instead you created a connection to that server, you can right click the item in list and select “Remove connection”.

[Tor]

Hi. Can you please verify that the resolution you want to use on the remote desktop (Linux and Windows) is listed among resolutions supported in display settings?

[Tor]

Hey Finnish, welcome back. 🙂 I see you’ve the ‘Resize remote screen’ option enabled, which overwrites the size requested by custom resolution setting. Try to disable it and let me know if the resolution is correct.

[Tor]

Hi. The Ctrl + Alt + Backspace is a quite “destructive” command, so I think we could find a way to solve your problem without adding the shortcut to the UI. 😀
I’d propose to remap the standard shortcut with something different, like Ctrl + Alt + End, which can be used on client without risking to kill the wrong X server.
You would need a procedure like this:

– Create the folder where to store a new XKB map entry:

mkdir -p ~/.xkb/symbols/

– In that directory create a file called local and edit it by adding the following configuration:

default partial modifier_keys
xkb_symbols "ctrl_alt_end" {
    key <END> {
        type="CTRL+ALT",
        symbols[Group1] = [ NoSymbol, NoSymbol, NoSymbol, NoSymbol, Terminate_Server ]
    };
};

– Run the following command:

setxkbmap -print | sed -e '/xkb_symbols/s/"[[:space:]]/+local(ctrl_alt_end)&/' | xkbcomp -I${HOME}/.xkb - $DISPLAY

– Press Ctrl + Alt + End to kill your X server 🙂

You can add the setxkbmap command to a script, and execute it automatically when the session starts, for example through a .desktop file in ~/.config/autostart.

[Tor]

Hi. We could not reproduce such behaviour, could you kindly answer some questions so we can investigate it?

– What is the NoMachine version installed on server side?
– What is the Android device model?
– Are you starting the connection through a LAN discovered server item, or by using a manual connection (configured with the wizard)?
– What is the reason why the server goes offline sometimes? For example is the server switched off, or is the device changing the subnet?

Please note that for the way the LAN discovery works the client could require some time to receive the information about the server, even if it should never take more than one minute or so.

[Tor]

Hi. The servers discovered in LAN are not visible in the list of connections when they’re not available: starting that connection would fail because the host doesn’t exist or the same IP could be used by a host in a different LAN.
You can create a static connection to that server by starting the wizard with the ‘New’ button, then use the server IP (you can read it by editing the LAN discovered server item) to complete the creation.

[Tor]

Switching to VP8 would not help because, as I said, the H.264 codec is only one of the reasons why there is a limit. We’ll release shortly (couple of weeks) the version with the improvement I’ve explained.

[Tor]

Hi.
The maximum resolution is limited for a bunch of reasons (e.g. H.264 has a maximum frame size), but we’ve implemented some improvements allowing us to be more complaisant. 🙂 Thanks to this, in our testing version we’ve doubled the maximum resolution.
The change is documented here so you can subscribe to be informed when it’ll be released:

https://www.nomachine.com/FR09Q03868

If you’re connected to a virtual desktop and if your client supports a resolution width bigger than 4096 you can enable the remote resize (from Display toolbar) and increase the window size up to the resolution you need. The client will try to reach that resolution to work around the custom resolution size constraints.

[Tor]

We’ve worked on a solution like this years ago, but during our testing the experience with some games was not very friendly because the mouse pointer was released in the worst moments! 🙂 Even after some tweaking we never reached a perfect solution covering all test cases, so in the end we gave up. Since you’ve shown some interest we could eventually include this pointer release mode through a configurable option. I’ll discuss it with UI designers.
Thank you for your feedback. 🙂

[Tor]

Thank you for your feedback, I’ll make sure we track it and find a way to inform how the mouse pointer grabbing works.

[Author]

Posts