How can I understand if a 3.5.0 session can't be reconnected because of different geometry or depth?
When and NX 3.5.0 user wants to reconnect to an existing NX session, nxclient determines the possibility of reconnection depending on two main parameters: screen depth and render extension availability.
When the NX client connects to the NX server, it asks for the user's session list.
The session list command is logged in the sshlog in "User NX Directory/temp/<pid>", usually in $HOME/.nx/temp/<pid> (where PID is the process ID of the nxclient logging) as follows:
NX> 105 Listsession --user="username" --status="suspended�54running" --geometry="1280x1024x32+render" --type="unix-kde"
The "geometry" parameter in the command above reports the size and the depth of the local X server as well as the render extension availability (if the render extension is not available, the "+render" string is not appended).
The NX server replies by sending the session list, which is shown in a window opened when there is a choice to reconnect to a session. Each session has its geometry and a services list.
The geometry is expressed in the form width x height x depth, e.g. 1024 x 768 x 16. To resume a session, its depth must be supported by the X server running on the client side.
The other parameter, " render extension ", can be seen in "Services" column of the Session list window; if it contains the entry "R", the corresponding session is using the render extension. If the render extension is being used, but the local X server doesn't support it, the session can't be resumed.
You can enable/disable the render extension in the NX Client GUI--> start NX Client --> Configure --> General folder --> in the "Display" section select "Use custom settings" --> Settings --> section "Performance"
A related article explaining the NX 3.5.0 reconnection policies s: