I am also affected by this problem. However, going back to karmic ppa version does not solve the problem for me: With lucid ppa version the existing session on the server would just die upon new connection atempt, and a new session got created. With the karmic ppa version existing sessions stay alive, but an additional new session is always created (I am not offered the option to reconnect an existing session). Not much of a difference from the user's point of view. Could it depend on the client version (I'm using 3.4.05 or 3.4.07)? Or is it linked to some config option? I am quite confident I was using default options for freenx in karmic before I upgraded to lucid.
Haven't tried neatnx so far, but from comments I've read, it does not seem to be the panacea either.
Is there a point trying the testing ppa versions?
I am also affected by this problem. However, going back to karmic ppa version does not solve the problem for me: With lucid ppa version the existing session on the server would just die upon new connection atempt, and a new session got created. With the karmic ppa version existing sessions stay alive, but an additional new session is always created (I am not offered the option to reconnect an existing session). Not much of a difference from the user's point of view. Could it depend on the client version (I'm using 3.4.05 or 3.4.07)? Or is it linked to some config option? I am quite confident I was using default options for freenx in karmic before I upgraded to lucid.
Haven't tried neatnx so far, but from comments I've read, it does not seem to be the panacea either.
Is there a point trying the testing ppa versions?