Forum Replies Created
Would you tell me whether the problem arises connecting to a physical or a virtual display?
Did you notice if remote desktop is actually updating (e.g. clock changes after a minute).
Would you collect the server logs and send to forum (at) nomachine (dot) com?
Please uncheck the permission box in system preferences, then re-enable it. Let me know if it is effective.July 9, 2021 at 11:24 in reply to: Higher screen resolution without scaling Windows (server) & Mint (client) #34389
Hello. RDP leverages a virtual display driver to move the user session into a virtual screen which resolution can be undetermined. NoMachine captures the content of the physical screen, so user session keeps using a full-featured video hardware that impose resolution among a finite set of modes.
why is MS RDP able to login immediately to the server desktop, whereas NoMachine connection requires entering the pw twice?
That would be a new feature. At the present moment it isn’t possible to do it.
I think the Windows login screen defaults to English layout. You could copy your user settings to the login screen using the Windows control panel (see picture).
NoMachine always let user specify the proper account/credential to pass the Winlogon stage, without automatic forwarding of password strings.
Attachments:July 2, 2021 at 09:37 in reply to: NM crashing with error: Display failure detected on display #34295
Windows placed at 0,0 should not cause any harm. It is a valid position for a window like any other. Have you got any sample program to reproduce such problem? Or would you name the software you are using? If it is in-house software, would you tell me which graphical library it is built on?
You could send such information to forum (at) nomachine.com if you prefer.July 1, 2021 at 15:13 in reply to: NM crashing with error: Display failure detected on display #34275
Hello. Is it a well know application? I’d like to reproduce that problem.
We need to know if grabbing is not working properly. Please run xev on Ubuntu and check if KeyPress/KeyRelease events are logged when Ctrl and Shift are pressed together.
I think the Ctrl+Shift combo is intercepted by Ubuntu desktop.
Sorry, I don’t understand: did you upgrade NoMachine or Ubuntu?
So, which version of NoMachine are you using on client and server?
Hello. It is not clear to me if that occurred after the upgrade of Ubuntu or NoMachine.
Would you tell me which Ctrl+Shift combination doesn’t work to you? Which action is associated with?
Do you expect that keyboard shortcut doing some action in the server-side Windows desktop or in the client-side Ubuntu one?
Would you try if changing setting “Grab the keyboard input” has any effect on such issue?June 1, 2021 at 09:38 in reply to: Linux desktop frozen when connecting with NoMachine #33813
Hello. The screen nxoutput0 is in virtual NoMachine sessions. So the remote access is not using an existing Xorg display. It looks like the Xorg display on your server failed for misconfiguration. “Number of created screens does not match number of detected devices” means that you have too many Device sections in you xorg.conf. I would rename existing xorg.conf and xorg.conf.d/* into backup files then retry to configure Xorg from scratch.
Does it occur all the times? As Trouble Report already exist, but requires some conditions being matched: NumLock and CapsLock status is not preserved on Windows when it’s changed while the NoMachine window is minimized
In case the problem you are facing is different, would you provide any piece of information useful for us to reproduce it?May 19, 2021 at 10:54 in reply to: Keyboard: wrong chars being type (keyboard encoding?) #33528
It is likely a crash in lightdm or in the desktop environment (that is the compiz-based Unity Desktop in Ubuntu 16.04).
If you turn lightdm off, NoMachine will present an option asking you if you want to launch a virtual display server. You’ll get an X11 session although no X server is running on the physical display.
Hello. Here’s the TR: Right mouse button behaves like left button if Control key is pressed down