Forum Replies Created
-
Posts
-
It looks like the display server does not provide multiple resolutions when no physical screen is connected.
If you turn off GDM (or whichever display manager you are using) and restart NoMachine, a virtual display server is created. The virtual display provides multiple resolution (physical video output doesn’t matter).
mousomer,
I suggest to try the new version 5.2.11.
On restart, I’m once again stuck at low resolution.
Disable lightdm so it won’t restart on boot:
sudo systemctl disable lightdmI didn’t manage to replicate, yet.
I assumed you are using Xfce desktop, could you confirm?
Do you mind sending a screenshot of the display settings panel, too?
Client and server log file would be useful. Follow the document How to gather debug logs for support requests then send them to: forum (at) nomachine (dot) com
Did you try to raise the display quality (in NoMachine client settings: “Display”, “Change settings”, then move the “Quality” slider)?
Could you post a screenshot showing the blurry text, and another the connection information (Ctrl+Alt+0 in NoMachine window, then go to “Connection”).
This is possible if you have access to the server machine: open a terminal window and type
xevIt is possible xev is not installed, in that case install with
sudo apt-get install x11-utilsAfter you launched xev, a small window shows up and input events are recorded in the terminal window.
Leave xev running, don’t close that window.
When you connect to Ubuntu from remote, xev will print mouse/keyboard events in the terminal. Or nothing if no input event is forwarded.
Have you got the chance of launching xev tool on the Ubuntu desktop to check that input events are forwarded?
I think keyboard autorepeat mode is “on” in the virtual (server side) display. If you have a terminal emulator among the remote applications then you can turn autorepeat off using this command:
xset r offNotice that client-side autorepeat is not affected by this command, so nothing would change from the user’s point of view. You get problems because autorepeat is “on” for both client and server.
I think the default value should be “off”, likely this should be fixed in NoMachine server.
walttheboss, it is true that if you checked “Always create a new display on this server” it cannot be reverted through any GUI.
But on server restart, if a working physical display is found NoMachine doesn’t start the virtual display and connection to physical is allowed, no matter if you checked “Always create” or not.
In your case, PhysicalDisplays in node.cfg played a role: no X server was found with the specified display number, so NoMachine started the virtual display and assumed all connection are directed to virtual. As you stated correctly, the PhysicalDisplays line in node.cfg should be left commented out.
My ideal solution would be to provide a configuration file that details my setup; each line contains a description of a monitor. In an xml format the file could say which monitors should be used by NoMachine. NoMachine reads the config file and determines the best way to fill the screens.
That would probably help you, but please consider that editing an XML file couldn’t be a suitable solution for the majority of a few million NoMachine users that aren’t programmers 😉
In any case implementing what you are asking in a user-friendly way on all platforms is questionable.
There is no way to tell NoMachine client to get into that partial full screen, using two monitors of three. The only way is that you already found: use client in windowed mode and resize it to cover the two monitors you want.
Be sure EnableClipboard is “both” in server configuration (file /usr/NX/etc/server.cfg).
Please let we have a look to your log files. Please, follow this article: https://www.nomachine.com/DT07M00098 then send files to forum (at) nomachine (dot) com