Re: sawfish + xinerama dropping / unmapping windows

On Tuesday 27 October 2009 10:58:01 Janek Kozicki wrote:
> Guys, have you seen the latest comment at:

According to the X protocol manual, it is the failing resource id that 
is returned.  Hence on BadWindow errors, ev->resourceid should not be a 
valid window regardless of which request caused the error.  However, it 
seems that sometimes ev->resourceid is a valid managed window, which is 
then marked "gone" in the error_handler.  It is a mystery why this 
happens.  Perhaps a bug in Xinerama if it only occurs when it is used?

Note that error_handler does not unmap the window.  X error handlers 
must not interact with the X server.  I don't know where the window gets 

> Chris you said that firefox sometimes disappears for you? Maybe you
> can try printing the code numbers,

It might also be useful to check whether ev->resourceid is equal to
w->id or w->frame.

> Or somebody can check at source code of other window managers.

Neither TWM nor FVWM use the error handler to detect missing windows 
like Sawfish does.  Does anyone know of another window manager that uses 
the same technique?

	Timo Korvola		<URL:>

[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]