Forum Replies Created
-
Posts
-
Hi! After selecting the “Resize remote display” option did you click the “Fullscreen on all monitors” button? Going fullscreen is required to mirror the client monitors geometries and layout on server side.
I cannot seem to use Ctrl on Windows to send Cmd in Mac.
Do you refer in particular to copy&paste operations? Are there other shortcuts you’re not comfortable with as Windows user connected to a Mac desktop?
Like Britgirl said we’re working on the feature, but any additional information you could give can be useful.Hi. The language you select in the installer changes only the EULA, it doesn’t affect the software language.
Open NoMachine client, click Settings, select Appearance and choose your language in the combo box on the right page. We’ll check the reason why the language automatically switches to a different language, but the configuration above should be enough to solve your problem.Hi. We’ve no problems to use the Windows + Shift + Arrows key combinations on NoMachine windows, to move them between monitors, minimize, etc. Those are functionalities offered by the window manager and we never had to support them explicitely.
Can you maybe give more context or any information useful to run a few more checks on our side?(perhaps this can be adjusted with the wmctrl but I am not familiar with its options)
Apologies, I did a bad assumption! You can replace the action “toggle” with “add”, so it will only enable fullscreen and it won’t remove it when its already set.
Hi. Client stores the last window state and restores it when starting, and currently there is no way to avoid that.
You could do what you need with a tool like ‘wmctrl’ by creating a script to start the client, or by editing the script /usr/NX/bin/nxplayer in a way similar to this:exec "$NX_SYSTEM/bin/nxplayer.bin" "$@" & sleep 1 wmctrl -x -r nxplayer.bin -b toggle,fullscreen wmctrl -x -R nxplayer.binWe’ll evaluate adding a command line option to always start in fullscreen mode by ignoring the last saved window state.
You could configure the client CFG to skip that message, by setting the following key to ‘false’:
<option key="Show local desktop connection information" value="false" />Normally this CFG is located in $HOME/.nx/config, but you can start the client with an option to load the CFG from different paths:
/usr/NX/bin/nxplayer --config /path/player.cfgThe file ‘nxplayer’ is a script, you could edit it to add the ‘–config’ option.
Meanwhile we’ll check how to improve the conditions triggering that message to avoid to show it in similar environments.
Hi. When you see that message you could check the box “Don’t show this dialog anymore” and never see it again, for any local connections. Is it not working, or do you need to pre-configure a bunch of different clients and you want to skip the message completely?
Hi! Sorry, I was a “little bit” late with this answer.
Could you please contact us at forum[at]nomachine[dot]com? We’d like to send you a debug binary to retrieve some logs.Guess who got lost in a wormhole? 😛 My apologies. Ssssso I noticed a possible issue occurring when the client should restore a resolution when connecting to the remote desktop. Can you please set the 2560 x 1600 as custom resolution (you can find it in Display settings) and confirm that the geometry is correctly applied when the client automatically reconnects?
Thanks.Hi. The NoMachine window covering your screens gets different scaling factors, so it can’t cover correctly all the available monitors area. You can probably work around this by changing application properties. Right click NoMachine shortcut, select Properties, Compatibility tab and check the box “Disable display scaling on high DPI settings”.
Hello. We’ve found that KWin has issues with passive keyboard grabbing on Wayland. If you can confirm that the problem occurs when grabbing is enabled, then you can try to start the client with the following command:
/usr/NX/bin/nxplayer --activegrabHi. Apologies, the box should be CHECKED in order to disable mDNS. 😛 If you’ll no longer see that log when the box is checked then we’ll know who is printing it, but not why it is happening. Are you using a custom kernel or a particular configuration or system security enforcing software?
Hi. First time I hear something like this, we daily use Kubuntu 21.04 and unfortunately we can’t reproduce the issue, so we’d need your help to verify what is happening. First of all would you please start an X11 app (Xterm, for example) and check if you reproduce the same behaviour?
Hi.
Could it be that the server is set up to somehow block this on the client? (given it’s a client connection file this would surprise me!?)
Yes, server admin can enforce general security by not allowing clients to store credentials. If server is managed by you I doubt this is the case, but if you’ve an administrator, I’d contact him/her to ask for confirmation.