On Wed, 2004-01-21 at 11:16, Christopher Hart wrote: > So this evening I've hit the bug - 3 times. I'm not doing anything > special, but I did stumble upon an interesting quark to the problem. > Xine works after the "crash".
[...] > xiTK WARNING(_x_error_handler:215): X error received: 'BadLength (poly > request too large or internal Xlib length error)' xine seems to be able to deal with the error; many (most?) X apps don't do any error handling, so AFAIK they get killed by the default libX11 error handler. > xiTK WARNING(xitk_image_create_xitk_pixmap_with_depth:231): XShmAttach() > failed. If this is related, it could point to shared memory? -- Earthling Michel Dänzer | Debian (powerpc), X and DRI developer Libre software enthusiast | http://svcs.affero.net/rm.php?r=daenzer