Forum Replies Created
-
Posts
-
When we access the console we go through vSphere Web Client versus the NoMachine windows client.
Installing 4.2.x on the server effectively makes it so you cannot Log Out of your GNOME session, this is true if we use vSphere Web Client or NoMachine Windows client ( 4.1 or 4.2 ).
Going back to 4.1.x on the server eliminates this behavior and all works as expected.
Again there are no errors in any logs, we simply choose to Log Out of the GNOME session and the buttons in the dialog image I sent you [Cancel and Log out ]are not enabled OR do not respond to a mouse click. All we can do is hit the X in the top right to forces a termination of the dialog.
As there is no way to Log out of the session we must use nxserver –terminate to kill the session(s).
I checked the lightweight mode on the server by looking at the node.cfg file, it was off and I tried turning it on. shutdown/startup after change no effect.
There is nothing in the logs, through GNOME I simply choose System-Log out .. get the screen I sent you and their is no response. There are 4 of us using the FREE windows client to access our Linux servers; the 4.1.29_1 client and the 4.2.17_13 client have the same behavior around this issue. When we were using 4.1.29_7 on the server and there was no issue for any of us using the 4.1.29_1 client. As soon as we went to 4.2.17_13 on the server this behavior started.
At this point we are monitoring our session will nxserver –list and terminating from the server.
Discovered this also affects our console, which we access outside of no machine. Have uninstalled 4.2.17_13 and gone back to 4.1.29_7.