On Thu, 19 May 2005, Russ Allbery wrote:

> I'm going to reduce the severity of the bug to important, since the
> critical part looks like it was Enlightenment's fault.  It's either
> important or grave, depending on how reproducible the problem is.  I don't
> think this should be an RC bug for sarge, based on what we know so far,
> although if we find a quick solution I'll certainly try to get that
> included if there's still time.

Yup, that seems perfectly sensible to me.

> It sounds like something either in the Gtk libraries or in the window
> manager or elsewhere on the system resized the window (maybe to some sort
> of overflow or absolute value of a negative height?) and GTimer got that
> value back from gtk_window_get_size and dutifully saved it to the config
> file.  I don't know whether this was some sort of side effect of the hang,
> or if it's what caused the hang (I think there's some evidence that the
> latter may be the case, since clearly that window size causes bizarre
> problems for Englightenment).

That all makes sense.  I'd be a little surprised if the resize came before
the hang (I hadn't moved or resized the window when it hung, and
I've not had similar problems with any other application (nor
caught enlightenment enlarging windows unexpectedly)) although I had
switched desktops and I suppose it's always possible that this kicked it
off.


> > Reproducing the freeze could be difficult - is there anything I can do
> > to get you more information if/when it happens again?
>
> If you can get this to happen again, I'd really like to see what the
> GTimer process is doing during the freeze.  One or both of:
>
>     strace -p <pid>
>
> or
>
>     gdb /usr/bin/gtimer
>     attach <pid>
>     backtrace
>
> would be very useful.  This looks like it might be hard to track down.

I'll let you know what I discover ;-)  The enlightenment bug is #309831,
for reference.

All the best,

Julian

-- 
Julian T. J. Midgley                       http://www.xenoclast.org/
Cambridge, England.
PGP: BCC7863F FP: 52D9 1750 5721 7E58 C9E1  A7D5 3027 2F2E BCC7 863F





-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to