sps@mcnc.org (Stephen P. Schaefer) (08/10/89)
Version: 18.54.x Compiled with: gcc 1.35 Running on: VAX BSD4.3 X Server: Xqvsm, VaxStation 2000, Ultrix 3.0/UWS 2.0 Window manager: X11R3 twm Three problems in decreasing seriousness: I run my emacs as an X11 client. Several times a day I get a message in the window from which I started emacs, which looks like: Xlib: sequence lost (0x10000 > 0x230a) in reply type 0x0! Sometimes two or three of these messages will appear at once. They appear to occur after some X event, most often an expose. In all cases after such a message, the emacs either exits immediately or hangs (responds to neither keyboard nor expose events). The 0x230a number varies without recognizable pattern, so don't base any hypotheses on the 0x0230a number. On one occasion, the number in the place of 0x0230a was something greater than 0x10000, and the error message appeared something like Xlib: sequence lost (0x20000 > 0x1230a) in reply type 0x0! At first, this was happening several times an hour, and was unbearable. I had linked with the X11R3 library we had compiled with pcc. I believe that in that version, there were rare occurrences of the reply type being non-0. I am now using an emacs linked with the X11 library supplied with UWS 2.0, having removed from it the XvmsAlloc.o to in order to use the emacs malloc without symbol conflict, and thus the 4.3BSD calloc. With this version I have never observed the error message with a reply type other than 0. The problem is now less frequent. No other X11 client has exhibited this behavior. A second problem: When using the menu command under info, I appear to have close to a 1/2 chance of hanging emacs. The menu prompt appears, but no further response to the keyboard occurs. This problem appears different, because emacs does not exit in response and because no error message appears on the initiating window. A third problem: When holding down the control key and another key to get autorepeating, the ``control'' modification will sometime get lost, and I'll get a sudden line of ffffffffffffffffffff in my buffer instead of the cursor positioned further along. This might be no more than a bad contact in the keyboard or a tired pinky, but it doesn't feel that way - the cursor will already have moved part way across the line before this behavior starts. Thanks in advance for any ideas. Thanks in perpetuity to the Free Software Foundation. -- Stephen P. Schaefer, Postmaster MCNC sps@mcnc.org P.O. Box 12889 ...!mcnc!sps RTP, NC 27709