December 2, 2015 at 11:09 #9220vnaipaulParticipant
I’m working through an evaluation of NoMachine Cloud Server v5, and have run into a problem with logins after a graceful user logout of a NoMachine-spawned virtual desktop (Xfce).
After logging out gracefully from the Xfce session launched from NoMachine, NoMachine reports “Ooops ! The connection to the server was lost”, and subsequent attempts to log in from the same browser session result in NoMachine hanging at ‘Connecting to …’.
Some details about my environment:
– NoMachine Cloud Server Evaluation v5.0.53 on CentOS 6 (single server/node)
– virtual displays only
– Xfce Desktop Environment v4.8.0
– Client web browser is Firefox (v38.4.0) on RHEL 6.7)
Detailed sequence of operations leading up to this problem:
1. From a new browser session, login at the nxhtd URL
2. Choose New Desktop, which runs xfwm4 –daemon and startxfce4 from ~/.xsession. The xfwm4 processes appear to exit after startxfce4 is exited (from the user logout),
3. Logout gracefully from the Xfce session (after updating Privacy settings in NoMachine session to not delete logs)
4. After the Xfce session ends, NoMachine reports “Ooops ! The connection to the server was lost”. Press [OK] to return to NoMachine login prompt.
5. Re-login to NoMachine from the original web browser session results in hanging at ‘Connecting to …’. A new NoMachine login from a fresh web browser session does work.
I’ve gathered debug logs, please let me know if this issue is something you can help with and I’ll send the logs, or any other information required.
ValDecember 2, 2015 at 15:49 #9228HavenContributor
Thank you for taking the time to report this.
We reproduced the issue in our labs. Here is the relevant Trouble Report:
Please use the “Notify me” to know when a fix is available.December 3, 2015 at 10:03 #9233vnaipaulParticipant
Thanks very much, haven. Looking forward to the fix, which we would need before we can proceed towards a production deployment.
Fwiw, I realized the xfwm4 process I had been running from ~/.xsession is no longer needed now that I’m running startxfce4 (as opposed to running some X11 app directly, which I had been doing before).
Also, I expect this goes without saying, but in addition to the re-login being made to work (from the same web browser session) after the Xfce session is closed, I think the at-exit message shown to the user, ‘The connection to the server was lost’ could be re-worded so the user doesn’t think there is a problem, e.g. ‘The connection to the server is closed.’ (without “Ooops”), or possibly even return the user to the prior NoMachine screen with the Existing/New Desktop choices, i.e. not requiring the user to press [OK].
– ValDecember 4, 2015 at 10:17 #9262HavenContributor
The “at-exit message shown to the user” will be fixed in the context of mentioned TR.
This topic was marked as solved, you can't post.