Tor

[Tor]

Hi. Is the file transfer working if you use the NoMachine tray menu on the server, or the Whiteboard window? Please try ‘Download a file from the server’ and ‘Send a file from the client’.

[Tor]

Hi. I suppose you’ve created a new connection and used 72.130.27.203:26300 in the hostname field. You can set the correct hostname by selecting the connection in the list and tapping Edit, then setting 72.130.27.203 as hostname and 26300 as port. Please let me know if this helps or, in the contrary case, tell me how you configure the connection so we can detect possible issues.

[Tor]

Hi batu. We’re working on a redesign of the tablet interface (like we did previously for the small displays version), which is the main reason why we didn’t release updates. A few weeks ago we rearranged our priorities and started to work on an app version including all features and fixes that are sitting there since some time. I’m sorry for this delay, I can guarantee we care a lot about the mobile version and we’ll update it very soon.

[Tor]

Hi. You’ll find here the information you’re looking for:

How to disable or re-enable Welcome panels shown at session startup
https://www.nomachine.com/it/AR11O00951

[Tor]

Hi. Are you using the latest NoMachine version? What is the protocol you’ve selected, NX or SSH? Can you give details about the proxy configuration you’re using (system proxy, automatic, etc)? Thanks.

[Tor]

Hi. NoMachine can only access files stored in its sandbox, that is the folder you see when doing file browsing. In order to upload your key, connect your phone to your computer, open iTunes, select the device, select “File Sharing” on the left side menu, select NoMachine in the list of applications, click “Add…” and select your key file. After doing this you can add the key to your connection file.
Our next release will include the integration with Files app, so you can move files to NoMachine sandbox more easily.

[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.

[Author]

Posts