Forum Replies Created
-
Posts
-
Hi. 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?
Hi. The error printed by the client is misleading, it should have stated clearly that there is a problem with the proxy configuration. We’ve documented this wrong error reporting here:
https://www.nomachine.com/TR07S10321
As for the reason why the proxy configuration is wrong, this is not clear yet. Can you try to select “Use system proxy setting” instead of “Automatic proxy configuration”? Is your system actually configured to use a proxy?
If you’re not sure about it but you know proxy parameters, you can select the manual configuration and fill it with the correct proxy host and port.Hi. Qt is using the X server properties and system environment to determine how to paint widgets, so we could compare the two different working environments to understand how to fix your issue.
Are you connecting to a virtual or to a physical desktop? What is the server operating system version?
You can run the commandsxdpyinfoandenvin your local or SSH terminal (where the application has the correct style) and in the remote NoMachine desktop, then attach the outputs here or to an email to forum[at]nomachine[dot]com. I’ll gladly check them to answer your doubts.Hi! All settings you change while connected to the remote desktop are saved and automatically applied when you connect again.
What is the distribution of the server? Are you connecting to a physical or virtual desktop?
Can you describe what you see exactly? For example, the session starts in fullscreen then goes back to window mode?
Did you try to change other settings, like a checkbox in Input or Display settings, in order to verify if those preferences are correctly saved?
Are you connecting to a server configured manually, or to a server automatically discovered in your LAN?
Thanks.Hi!
You can press Control + Alt + ID to switch monitor, where ID is 1, 2, etc. If you want to know the ID of each monitor, press Control + Alt + I. You can also configure these key bindings from menu Input, Shortcuts.Hi Martin.
You can open the Display menu by pressing Control + Alt + 0 and by clicking the Display item.
In order to know if your window manager can be configured to show thick window borders we’d need to know the operating system version running on the server, as this is a system configuration.Hi. We have a similar issue documented here:
https://www.nomachine.com/TR10Q09439
During our tests we’ve found this issue occurs when Sticky Keys are enabled on Windows, could you please verify if that is your case? The configuration can be checked in Settings, Ease of Access, Keyboard, Use Sticky Keys.
Hi. Is the ‘Scale to window’ option enabled in the Display menu? If the remote desktop is being shrinked in the window, grabbing a window edge could be difficult if the remote window manager has a tiny sensitive area since it’ll be reduced even more by the scaling down effect. If this is the case you could disable the scaling mode, or configure the window manager to show bigger window frames.
Nothing changed between my initial report and now.
So far we could not reproduce the issue you’re describing, with the Gnome configuration I’ve suggested above. Could you contact us at forum[at]nomachine[dot]com, so we could send you a client automatically dealing with the compositor requests in order to exclude some trivial problems?