control: tags -1 +moreinfo > `gkrellm` stopped working a while back for me (can't say for sure when it > started). > It crashes soon after displaying its window for me. The error message is: > > % /usr/bin/gkrellm --sync > The program 'gkrellm' received an X Window System error. > This probably reflects a bug in the program. > The error was 'BadPixmap (invalid Pixmap parameter)'. > (Details: serial 5672 error_code 4 request_code 56 minor_code 0) > (Note to programmers: normally, X errors are reported asynchronously; > that is, you will receive the error a while after causing it. > To debug your program, run it with the --sync command line > option to change this behavior. You can then get a meaningful > backtrace from your debugger if you break on the gdk_x_error() > function.) > % > > I tried starting it under `gdb`, setting a breakpoint on `gdk_x_error` > and starting it with `--sync` but the breakpoint is never hit (and it > seems this gdk function is never even defined). > > This occurs on all of my machines running Debian testing.
upstream suggested these steps: ``` Does moving/renaming $HOME/.gkrellm2 avoid the crash? I think I have seen crashes before with certain older gkrellm themes, starting with a fresh configuration would avoid that. Another try would be to start gkrellm with all debug logging enabled from a terminal and see how far it gets, i.e. gkrellm -d 32767 ``` can you try them and let this bug report know? thanks