Re: Xlib:sequece lost. Continued.

Sorry to inform you, but the patch did not solve the problem. I patched the 21.5-b8 version and after a few hours of work - it froze with the Xlib: unexpected async reply (sequence 0x29945)! Xlib: sequence lost (0x39b1c > 0x29b1c) in reply type 0x0! xemacs: X Error of failed request: BadImplementation (server does not implement operation) Major opcode of failed request: 20 (X_GetProperty) Serial number of failed request: 170780 Current serial number in output stream: 170780 Xlib: unexpected async reply (sequence 0x29b4d)! It may be important that the patched version produced much more messages of that kind than the original one. Michael Sperber [Mr. Preprocessor] wrote: "Alexander" == Alexander Sirotkin <Sirotkin> writes: Alexander> I've submitted a bug report through xemacs a few days ago, not sure if Alexander> you actually received it. Alexander> It's about xemacs freezing and getting the Alexander> Xlib: sequence lost (0x80000 > 0x785af) in reply type 0x1! Alexander> error. Alexander> Just wanted to add a few details : Alexander> I think (although I'm not sure) that this problem happens more aften Alexander> when I work with ClearCase. There are two differences in this case: Alexander> 1. I work with mvfs filesystem and xemacs may have an issue with mvfs Alexander> (or mvfs may have an issue with xemacs :) Alexander> 2. It may not be directly connected to mvfs, but mvfs is actually very Alexander> slow - Alexander> may be this fact triggers the above error. Could you try the patch at http://list-archive.xemacs.org/xemacs-patches/200207/msg00189.html <http://list-archive.xemacs.org/xemacs-patches/200207/msg00189.html> and report back? -- Alexander Sirotkin SW Engineer Texas Instruments Broadband Communications Israel (BCIL) Tel: +972-9-9706587 ___________________________________________ Are you using Windows or is that just an XT?