But then if I log out and log back in again, I get errors as GNOME tries to re-apply the monitor settings. I can change the monitor resolution from within Ubuntu's System Preferences in the NX session. Once in the NX session, I am able to hit Ctrl-Alt-R once or twice (depending on which mode the session is started in) to switch to auto-resize mode and force the NX session back to the size of the client window. Has anyone experienced this issue? I found a couple of workarounds, but nothing to indicate why my NX session blows up to 1920x1200 in the first place.
I tried to repeat this test using the NoMachine client on a Windows 7 machine and I got similar results. In both cases OpenNX briefly displays a window of the desired size, before resizing to take up my whole Mac desktop with the even bigger 1920x1200 GNOME session underneath. The Riverbed AirPcap Product has reached End of. I tried manually setting the resolution to 800圆00 in OpenNX but this too got forced to 1920x1200. Windows 7 Windows 8 Windows 8.1 Windows Server 2008 R2 Windows Server 2012 Windows Server 2012 R2. Now whenever I connect the NX session is forced to the native 1920x1200 resolution of the monitor attached to the server, rather than the client screen area. However, this behavior changed recently (with an update, I think). I have been using OpenNX on a Mac to connect to a NoMachine 3.5 server on Ubuntu, and I was able to start a new GNOME session with the using the available screen area.
0 kommentar(er)
