On Sat, 28 Jan 2006, Bernhard R. Link wrote:
* Viktor Griph <[EMAIL PROTECTED]> [060128 14:36]:
I've done some tests and belive that this bug is due to a change in X with
XOrg 6.8. I've tested fvwm 2.5.16, 2.5.10 and 2.5.4 from the 2.5.x branch,
and all have the bug. However I'm sure that the bug was not present when I
used 2.5.4 (and probably not 2.5.10) actively. Thus it must be something
else that has changed since then. The bug is however not present in
2.4.19, so it must be soemthing that has changed in the early 2.5.x
versions, which I weren't able to compile now.
I'm seeing the bug here with the Debian sarge version of XFree86 namely
4.3.0.dfsg.1-14sarge1. I do not know if it contain any patches taken
from Xorg, though.
Hochachtungsvoll,
Bernhard R. Link
Well, I really don't know about that. thinking about it the only x-server
I'm certain it has worked with is a version of Xsun on solaris 2.8.
Looking at the fvwm code I believe it might be that an XSync has been
changed to an XFlush in the startup code before changing the errorhandler
from the one that traps running WMs to the normal fvwm error handler. But
since I'm not sure exactly how this WM-trapping is supposed to work I
leave to someone else to decide if changing it back to XSync is correct.
/Viktor
