Forum Replies Created
-
Posts
-
Would run pmap to explore memory allocated by nxnode.bin? That is:
pmap -p NNNN -X > nxnode.pmap
(put nxnode.bin process ID in place of NNNN).This is what happened: in graphical.target NoMachine shares the existing Xorg display. In multi-user.target it creates a new virtual display on demand. The NoMachine virtual display does not rely on graphical hardware and just ignores xorg.conf.
I think that using NoMachine “virtual display” sessions along with feature FR12K02799 you’d achieve the closest thing to the RDP behavior you described.
Did you try to run with graphical.target, placing your xorg.conf in /etc/X11, even when no display is connected?
If Xorg refuses to work correctly, you can simulate the presence of a monitor using a physical dummy display plug.
Otherwise dump EDID from the real display and force it in xorg.conf, but I’m afraid this latter could damage a monitor of different kind if accidentally attached.See: What is the difference between physical desktop and virtual desktop
By installing any of the products from the NoMachine for the Enterprise range (except Enterprise Desktop and Cloud Server) instead, you can run “virtual desktop sessions”. The virtual desktop functionality allows individual multiple Linux desktops to run on the same host. Each user can have their own personal ‘virtual’ Linux desktop according to how the Administrator has configured it.
FR12K02799 is not implemented, yet. You can select option to be notified about progress. By the way, check if you need a “virtual session” or a “physical desktop sharing” at first. In the latter case, maybe you need to add virtual screens in your virtual machine.
Hello, I guess you are using virtual display sessions, in that case is this feature what are you searching for?
https://www.nomachine.com/FR12K02799This post may help: NoMachine keyboard switch
So do you have a remote display with a Polish layout and when connecting by NoMachine it switches to US? Do I understand it correctly?
Yes, the dongle is physical, so it is not the correct option of a virtual machine. This suggestion could help: Setting display resolution beyond 1024×768 with headless Windows 10. I didn’t test it on my own but you could give it a try (as usual, be very careful editing the Windows registry).
You are right: RDP session creates a virtual display, while NoMachine provide access to the physical display.
The video output of the server is likely disconnected, or the monitor is turned off, so the video card shows just one default resolution.
If you don’t mean to attach a monitor to the server, could consider using a fake display dongle to make video card enable other resolutions.Thank you.
NoMachine does not use any of those “unsafe and deprecated” functions, by the way Fedora changed the suffix of libcrypt.so from 1 to 2. That is, Fedora now provides libcrypt.so.2 but NoMachine depends on libcrypt.so.1.
So that’s why, at the moment, you need libxcrypt-compat package to restore the required dependency from libcrypt.so.1.
Try to run “visudo” and remove the word NOPASSWD from the active line (no heading #) where you see:
(ALL : ALL) NOPASSWD: ALLYes, those buttons are toggles for enabling and disabling. So toggling “Resize remote” helped.
If the behaviour continues, we’d need to have specific steps and environment details in order to be able to try and reproduce it.Hello. Version 6.6.8 added H.264 encoder to the free edition, so it is likely your installation started using it after you updated Windows 7 server.
The description you provided would point towards a problem in the client side H.264 decoding.Could you tell us if checking option “Disable client side hardware decoding” is enough to fix the issue?
Would you send client and server log data to the address: forum (at) nomachine (dot) com?
Client log: Create zip of folder %USERPROFILE%\.nx
Server log: Create zip of folder %PROGRAMDATA%/NoMachine/var/log