On Sun, 25 Sep 2005 at 12:32:07 -0400, Thomas Dickey wrote: > On Sun, Sep 25, 2005 at 04:50:14PM +0200, Jan Gorski wrote: > > On Sat, 24 Sep 2005 at 19:25:52 -0400, Thomas Dickey wrote: > > > (That would be "configure --enable-trace --enable-wide-chars > > > --enable-luit", > > > and the executable produces Trace-parent.out and Trace-child.out) > > > > Well, I've run it. Traces are in http://slimak.info/~slimak/traces.tar.bz2 > > if > > you want to look at them. All hangs end with this line > > thanks (got a copy for reading)
For some time I was using xfce4-terminal and xfce4wm to avoid this bug (and another one, 329916). At least month ago I gave a try to fvwm again, and it was working --- till last upgrade :). Now I have checkd it in few configurations, and it seems, that both bugs depend on xinerama(1)... Bug 329916 is a bit upredictible, and sometimes it takes a moment till it appears, but this bug is easier to reproduce, so maybe somebody can tell me what else can be done to find out what happens? Cheers Jan Górski (1) adding Option "Xinerama" to sigle monitor configuration does not trigger problems, so maybe not xinerama, but something else connected with using two monitors... -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
