Re: [trinity-users] FreeNX generating multiple (frozen) NX client sessions

Hello, I have TDE installed on a CenOS 6.3 VPS in the cloud, which i use an NX client to access. There seems to be a wierd interaction between TDE side and top panels and FreeNX. I was in the process of adding application icons to the top panel when I was queried by dialog indicating that some part of this process was taking too long (I don't remember the exact message) and did I want to stop the process? I clicked yes, unfortunately. Now nothing works the way it did before. When I try to connect to the server with the NX client, I get multiple session windows, and all of them are frozen (mouse does not work internal to the session window). I can drag the window from its top bar, but I can't close it, either with the X button or with "close" in a pop-up dialog box. A strange aspect is that these session windows are now numbered in their top bar with <2>, <4>, etc. centered. And in the panel popup of my client machine associated with the NX icon, these numbers appear. When I click one of them (from the client), I will get one of these "windows" displayed. It might be just a top bar (actually an empty TDE top panel labeled with a <number> with no window below it, or an empty side panel labeled with a <number>), and it might overlap a complete window (labeled at the top with some other number, e.g. <6>). Some of these windows will have the side and top panels that I had populated before my fatal "yes" click, but they do not respond to mouse button events. The only way to get rid of these windows is the kill the nxssh processes on the server (which happen to be hogging all of the server's CPU time). Then I ran nxserver --terminate <username> getting rid of all of the old NX sessions for my username "bear" and "root". Then rebooted the server, and tried logging in again from my client machine using the NX client. The same multiple-session behavior happened again. There should have been only one NX session window. But there were several. The same thing happened when loging in to root. Does anybody have a clue as to what I can do? TIA, Bear --