Bob Woodside <[EMAIL PROTECTED]> writes: > On Tue, 29 Apr 2003 22:52:48 +0200 > Olivier Chapuis <[EMAIL PROTECTED]> wrote: > > > I've installed an X error handler to FvwmIdent. Now FvwmIdent should > > core dump, the gdb output may help us to determine if this error is > > acceptable or not. I guess that if you remove the #if 0 code of > > FvwmIdent.c (ErrorHandler) FvwmIdent should work again. > > > > I cannot reproduce your problem. What is your FvwmIdent config? > > Wow! I didn't even think about its config, since there's not that much > to config. It turns out that I did have some config lines left over from > antiquity, lurking in one of the files (my .fvwm2rc is nothing but a > series of Reads of subordinate files): they set the Back and Fore colors > in the old-fashioned way, e,g., > > *FvwmIdent: Back MidnightBlue > *FvwmIdent: Fore Yellow > > If either of these lines is present, the problem occurs. With neither of > them, all is well. > > Needless to say, I switched to using a Colorset immediately (which > works fine, of course).
I run FvwmIdent with: *FvwmIdent: Back Black *FvwmIdent: Fore white *FvwmIdent: Font 9x15bold no problem here, but I missed the version you had the problem with. I don't get any errors running with current CVS. -- Dan Espen E-mail: [EMAIL PROTECTED] -- 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]
