show stopper in xfwm4

edscott wilson garcia edscott at imp.mx
Mon Sep 1 23:48:21 CEST 2003


On Mon, 2003-09-01 at 16:32, Olivier Fourdan wrote:
> Edscott,
> 
> Well xfwm4 will core if there is a bug, otherwise kill -11 its pid and
> you should get a core...

I lost the chance for a core when I gave it a kill -9 thinking the
message from the netload plugin was from xfwm4. Oh, well, next time it's
a kill -11.

regards,

Edscott

> 
> Cheers,
> Olivier.
> 
> On Mon, 2003-09-01 at 23:18, edscott wilson garcia wrote:
> > On Mon, 2003-09-01 at 14:38, Olivier Fourdan wrote:
> > > Hi Edscott,
> > > 
> > > On Mon, 2003-09-01 at 17:07, edscott wilson garcia wrote:
> > > > I came across a showstopper in xfwm4. On clicking the [-] from the title
> > > > bar, I doubleclicked simultaneously with the mouse move and the window
> > > > did not close nor did the menu appear. 
> > > 
> > > I cannot reproduce that here. And I hardly see how this can happen given
> > > the code that handle this in xfwm4. This could come from gtk itself.
> > > 
> > > Where you rinning from a remote display? What's your gtk version?
> > 
> > I've tried to reproduce it but without luck. I was running from local
> > display, with gtk 2.2.2.
> > 
> > > 
> > > > Xfwm4 went into an endless loop.
> > > > Output on terminal on which X was running was:
> > > > 
> > > > Max = 1249
> > > 
> > > That's not from xfwm4 at least.
> > > 
> > > > printed about twice a second.
> > > > Apparently the maximize menu entry got a signal before it was supposed
> > > > to and xfwm4 looped trying to figure out the maximization borders. It is
> > > > very rare and difficult to reproduce, but it will force an X shutdown.
> > > 
> > > That doesn't make much sense. If you are able to reproduce the problem,
> > > a gdb on the running process would tell where it is looping...
> > 
> > >From Bernhard mail, the loop text was not from xfwm4, so the bug is most
> > probably a race condition in gtk. Is there a way to signal xfwm4 so that
> > it will drop a core file? That would come in handy to pinpoint the place
> > where xfwm4 could be stopping. 
> > 
> > regards,
> > 
> > Edscott
> > 
> > > 
> > > Cheers,
> > 
> > _______________________________________________
> > Xfce4-dev mailing list
> > Xfce4-dev at xfce.org
> > http://moongroup.com/mailman/listinfo/xfce4-dev




More information about the Xfce4-dev mailing list