Forum Replies Created
-
Posts
-
It’s me again. Can you please save server side logs and send them to forum[at]nomachine[dot]com? You can do that by opening the NoMachine client > Settings > Server > Security > Take logs (below in the panel) and select where to save the file. We’d like to identify some operational parameters that are common in the issue I mentioned in my previous post.
Would you like to install a package implementing a potential fix for your problem? We’d just need to know what is the product you installed on the server machine (if you’re not sure about it, open NoMachine client > Settings > Server > Updates).
What type of Mac hardware do you’ve on server side (macbook, iMac, etc) and what processor does it use (Intel, Silicon)? We’ve already started some internal tests, but the more we know the better it is. I’ll keep you updated.
Hi. Can you please share a few details about your client and server OS version and working environment? We’re not aware of issues so we’d need to run some tests on your specific configuration.
Hey there. We’ve found the issue and documented also a workaround:
https://kb.nomachine.com/TR06W11407
The fix will be included in the next maintenance which is to be released shortly.
@thibaut the client mode being reverted could be caused by a client process overwriting your change, so if you want to test that, be sure to close all running nxplayer instances.
Additionally can you confirm if, like @wernermaes, you’re using the SSH protocol to connect and agent forwarding to authenticate?
We’re still in process of investigating the behaviour, but of course it is not expected so there is nothing wrong on your side.
Could you please export client side logs (Settings > Security > Take logs) and send them to forum[at]nomachine[dot]com? We’re like to address this issue quickly, any hints will be helpful.
Hi. We didn’t find issues with the greeting message. Could you please confirm name and version of your Linux distribution and Desktop Environment on the server?
If you press ESC while you’re viewing the remote desktop, you’re just sending the key to the remote active application so it won’t have any effect on the client (with or without keyboard grabbing).
Next time you use NoMachine you could get a couple of screenshots to show what you’re trying to do. If you don’t want to publish them here, you can send them at forum[at]nomachine[dot]com.Hi. You can use one of the following methods to switch the active Space:
- Open the Keyboard from the right toolbar and press Control + Left/Right in the extended keys bar
- Add Mission Control in the top right Hot Corner, then switch to the pointer mode from the right toolbar, trigger the corner, select the desktop and switch back to touch mode
We’re working on an improvement based on a gesture similar to the one you use on the macbook trackpad (four fingers swipe), it requires some additional changes to support correctly all server operating systems, but we should be almost ready.
Hi. Are you using the NoMachine window in fullscreen mode? If you do, you can Control + Option + M to minimize, or Command + Tab to switch to other local windows (this second method only works if you didn’t enable the keyboard grabbing, in such a case the shortcut would be sent to the remote desktop).
If you’re not using fullscreen, would you mind explaining where you’re pressing the ESC/Alt/etc keys, and what do you see on screen?Hi. Did you maybe notice if the issue occurs when switching the resize mode from “Scale to window” to “Resize remote display”? We reproduced a similar problem with that resize mode switch and we also noticed that in this particular state the client scales the desktop instead of resizing it, so you could verify your client resize configuration and change the window size to confirm if you’re having the same issue.
Hello and thank you for the detailed info. It seems there is a problem to access the fonts database to initialize the application.
You can try to validate all fonts in order to exclude that any of them is corrupted. You should open Font Book application, select an item in the fonts list, press Command + A to select them all, then use the File > Validate selection menu. Let me know if you’ve one or more troublesome fonts.
If this doesn’t help, could you kindly try to create a new user on your macOS, and check if with that user the NoMachine client opens correctly? With a new user the fonts cache would be empty, so we would confirm if there is a problem with the cache before cleaning it up.
Thank you for your help.