You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What steps will reproduce the problem?
1. connect to server with NX Client for Windows configured for KDE (4.x)
2. After some time, maybe 1-2 hours, the connection is lost. Reconnect and
the session is restored.
3. the session then loses a connection within minutes.
What is the expected output? What do you see instead?
When I reconnect/resume a KDE session, I lose the connection within minutes
instead of hours when I started a fresh session.
What version of the product are you using? On what operating system?
hip pygowave_project # eix neatx
[I] net-misc/neatx
Available versions: (~)0.3.1_p43-r1
Installed versions: 0.3.1_p43-r1(12:29:37 10/08/09)
Homepage: http://code.google.com/p/neatx/
Description: Google implementation of NX server
hip pygowave_project # dmesg | grep 'Linux version'
[ 0.000000] Linux version 2.6.30-gentoo-r6 (root@livecd) (gcc version
4.3.2 (Gentoo 4.3.2-r3 p1.6, pie-10.1.5) ) #1 SMP Wed Sep 30 17:32:14 PDT 2009
hip pygowave_project #
Please provide any additional information below.
The work-around is to immediately shutdown the KDE session upon reconnect
and, if successful shutdown is achieved, launch a new NX Client session
thereafter which will persist until the shutdown problem reoccurs after an
hour or two.
The problem is I configure my KDE session with a variety of open consoles &
etc. and have to start all over again once I've restarted a stable session
of KDE.
Original issue reported on code.google.com by jlpool...@gmail.com on 15 Oct 2009 at 4:12
The text was updated successfully, but these errors were encountered:
Can you please post the full session logs (from session start, through session
disconnect/resume, to session redisconnect) from /var/log/user.log please?
Thanks,
Steve
Original issue reported on code.google.com by
jlpool...@gmail.com
on 15 Oct 2009 at 4:12The text was updated successfully, but these errors were encountered: