On 18 Apr 2002 15:13:59 +0100, Tim Phipps wrote: > > [EMAIL PROTECTED] wrote: > > >[FVWM][FvwmErrorHandler]: <<ERROR>> *** internal error *** > >[FVWM][FvwmErrorHandler]: <<ERROR>> Request 56, Error 13, EventType: 0 > >[FVWM][FvwmErrorHandler]: <<ERROR>> *** internal error *** > >[FVWM][FvwmErrorHandler]: <<ERROR>> Request 72, Error 13, EventType: 0 > > > I think these are being caused by parse_colorset() using a GC that has > not been created. I just assumed that Scr.MonoGC would be OK. Here's a > patch that makes parse_colorset() create it's own mono GC. It also > includes a debug message that you should see excatly once
Unfortunately this patch does not change anything for me, so I suppose it should not be applied. I can't reproduce this problem with any simple config, including the original Dominik's one. However, the problem is fully reproducible using fvwm-themes. I even got core dump when changed one Plain colorset to gradient. This happens when I change colorset 10 in [EMAIL PROTECTED] to this: Colorset 10 DGradient 100 2 yellow 1 green 1 navy But I can't get a core dump trace (I don't know why it is empty). I tried to debug this problem, but something strange happens. The depth (8, 16, 24) does not matter. Simple configs seem to work ok. Please someone confirm or deny these 2 problems with fvwm-themes: 1) gradients do not work (they produce 4 error lines above) 2) core dump when changing one line in [EMAIL PROTECTED] Regards, Mikhael. -- Visit the official FVWM web page at <URL:http://www.fvwm.org/>. To unsubscribe from the list, send "unsubscribe fvwm-workers" in the body of a message to [EMAIL PROTECTED] To report problems, send mail to [EMAIL PROTECTED]
