Forum Replies Created
-
Posts
-
(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.
Hi. Thank you for sharing your experience, it is always great to know our users needs to improve the application.
The extended keyboard bar is mainly a way to integrate the virtual keyboard for quick or simple interaction with the remote desktop, as we expect an external keyboard to be the most suitable solution for heavy editing. However sometimes even a small task could require to press multiple times the same modifier (hello emacs users!), so we’ve started a bunch of tests and discussions to evaluate the best way to implement your proposal. The idea of the tap&hold to toggle the sticky keys is good, but we need to have some experimental versions and collect our testers feedbacks before confirming it.Sometimes system settings try to restore the resolution of X server when it changes to a geometry different from the one stored in monitors.xml. You could try to rename (not delete, so you can restore in later) the monitors.xml file and verify if the NoMachine client can correctly resize the desktop on startup.
If it still fails please follow this article to collect client and server logs, we’ll analyze them:If the file is writeable we can be sure settings are correctly saved, so the problem should be somewhere else. The client sends its resize mode request to the desktop, but the desktop could decide to change its geometry by forcing the client to adapt. If something like that happens the resize mode could be automatically switched to viewport, so let’s check if this is the case.
What are the resolutions of your local (client) and of your remote desktop before you resize it?
Can you verify if the file~/.config/monitors.xmlexists on the server?
When you login to the remote desktop, do you land immediately in the desktop or in the remote login window?Thank you for the answers.
I have the connection saved on an nxs file in the desktop, although I’m not sure if this is relevant (I guess not).
This is usually not a problem, you just need to be sure that your NXS file can be modified by checking the write permissions. If you confirm they’re correct, I’ll explain how to gather a log file to retrieve further information.
I have a desktop machine; this is the nx server.
Do you know what is the Linux distribution running on the server?