On Mon, Feb 04, 2008 at 10:30:03PM +0600, Roman S Dubtsov wrote: > On Monday 04 February 2008, Dominik Vogt wrote: > > Should be fixed with my latest commit. I think the X error should > > be gone too. Can you try it and look if the X error reappears, > > pease? > > I have attached a patch which checks image != NULL before calling > XDestroyImage(image). After this, FVWM does not crash,
I've applied the patch. > but my FvwmButtons-based panel does (see log attached). There is no output of FvwmButtons in there. Can you please post a stack trace in a new thread please? [snip] > [fvwm.1][parse_colorset]: <<ERROR>> error reading root background > [fvwm.1][parse_colorset]: <<ERROR>> error reading root background [snip] > [fvwm.0][parse_colorset]: <<ERROR>> error reading root background > [fvwm.0][parse_colorset]: <<ERROR>> error reading root background > [fvwm.0][FvwmErrorHandler]: <<ERROR>> *** internal error *** > [fvwm.0][FvwmErrorHandler]: <<ERROR>> Request 73, Error 8, EventType: 28 > [fvwm.0][parse_colorset]: <<ERROR>> error reading root background > [fvwm.0][FvwmErrorHandler]: <<ERROR>> *** internal error *** > [fvwm.0][FvwmErrorHandler]: <<ERROR>> Request 73, Error 8, EventType: 28 > [fvwm.0][parse_colorset]: <<ERROR>> error reading root background [snip] > [fvwm.0][parse_colorset]: <<ERROR>> error reading root background > [fvwm.0][parse_colorset]: <<ERROR>> error reading root background > [fvwm.1][parse_colorset]: <<ERROR>> error reading root background > [fvwm.1][parse_colorset]: <<ERROR>> error reading root background Oh my, you seem to get *tons* of these errors. It looks like some process updates the root backgorund and then immediately changes it quite often. Ciao Dominik ^_^ ^_^ -- Dominik Vogt
