

Or, if the OS is systemd-based: journalctl -b -0 > journalctl.txtĤ) Additionally, the following test could also provide additional information: xsession-errors file in the user's home.įor example: /home/nxtest01/.xsession-errors

When running a virtual desktop, however, it should be considered that the X display manager usually redirects the standard error to: ~/.xsession-errors and the NoMachine clients file can be empty.Ģ) The. The NoMachine node redirects the standard error of X applications to this file. When error 'application terminated prematurely' is present, it may be helpful to look for a possible cause of the problem in these files on the remote host:ġ) The clients file in the /usr/NX/var/log/node/C- directory.įor example: /usr/NX/var/log/node/C-testdrive2-1005-246612EE435B150D4A8D37463B948139/clients These files are stored in the NoMachine session directory created in the /usr/NX/var/log/node directory. Error: Session failed, application terminated prematurely.' NX> 598 Error: failed to connect to nxclient -monitor.Īnd in the session log file on the end-user's host:ģ579 3579 15:18:18 658.862 ClientSession: Failing reason is 'The session negotiation failed. NX> 501 Session failed, application terminated prematurely. When the application terminates immediately, the following error is reported in the connection log file: 'Run the console' or the program set in 'Run the following command'. Restarting the server is not necessary, this change will become effective when the new session is started.įor custom sessions, the application run by the node is specified in the client User Interface, e.g. Grep ^Exec /usr/share/xsessions/sktopįor further examples, please refer also to this article: ģ) Once you've retrieved the command, ensure it's set in the DefaultDesktopCommand key in node.cfg. Such command is written in the *.desktop file in the line starting with Exec. In order to check if the command is correct, you can do the following:ġ) Find out which is the desktop environments installed on your system by executing this command in a terminal:Ģ) Then retrieve the command to start the desktop of your choice. The command to start the Linux desktop environment is defined in the DefaultDesktopCommand key in the node configuration file (/usr/NX/etc/node.cfg).ĭefaultDesktopCommand "/etc/X11/Xsession 'gnome-session -session=ubuntu'" This can happen when the command specified for launching the desktop or the custom application is not appropriate. the desktop environment or a custom application) terminated immediately after being started. It means that the application run by NoMachine node (i.e. Error: Session failed, application terminated prematurely."

If the user gets this message when connecting to a Linux host:
