>> Install xrdp. Run rdesktop localhost, and log in as a vanilla debian >> user with no special customization. Start emacs 23. Hit ctrl-k in >> emacs. rdesktop exits. > >> You can also reproduce this by connecting to your xrdp server with mstsc >> from a Windows box and doing the same test. In this case as well, the >> remote desktop client exits. Emacs does seem to receive the CTRL-k. > >> Other uses of ctrl-k do not cause a problem. > > I am unable to reproduce this problem. Could you try starting emacs > with "emacs -q"? Also, please try with to start a new session through a > VNC server to check if it also happens through a VNC session.
Same with emacs -q --no-site-file. If I just run Xvnc and connect with a vnc viewer, I don't see a problem. Looking into it a little more, neither xrdp nor Xvnc crashes. In fact, if I do a ps auxw before and after hitting ctrl-k, there are no changes in which processes are running, and when I reconnect, my session is still there, and the ctrl-k has been properly consumed by emacs. The problem appears deeper than this. I'm trying to find various other ways to reproduce this, and I'm finding that my session just won't stay up. It is continually disconnecting. I'd welcome suggestions on how to debug this. I have plenty of programming experience, so I could dig into it and probably get somewhere, but if you have any tips, it would be helpful. I'm a little puzzled as to why no one else is seeing it. It would be very nice if it ends up being something odd about my environment, but that's why I've gone about this by starting with a vanilla user account with no special customizations. Anyway, I don't even really know the anatomy of this thing....what starts what, what the components are, who does the translation between vnc and rdp, etc. Anyway, it seems clear that something that xrdp (or whatever is actually talking rdp) is sending to the client is causing the client to exit. I've tried this with two versions of rdesktop as well as with the terminal services client in Windows XP. Anyway, I'll try to dig deeper. Any pointers would be appreciated. --Jay -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
