[Debichem-devel] Bug#452939: Bug#452939: still not fixed
Daniel Leidert
daniel.leidert at wgdd.de
Wed Jan 16 12:30:15 UTC 2008
Am Mittwoch, den 16.01.2008, 09:32 +0100 schrieb di dit:
> Sorry, but this bug isn't fixed.
Well, it did not longer crash for me, so we thought, the bug has been
fixed. Seems there is still a problem.
> I've been unable to test the fix earlier. Sorry for the long delay.
No problem.
> Testing with a current unstable system (which means that parts of the
> xserver have been updated since the original report) returns the
> following error on my amd64 setup with the radeon Xorg driver, trying
> to save a PNG:
>
> $ gcrystal /usr/share/doc/gcrystal/examples/nickel.gcrystal
> The program 'gcrystal' received an X Window System error.
> This probably reflects a bug in the program.
> The error was 'BadDrawable (invalid Pixmap or Window parameter)'.
> (Details: serial 13551 error_code 9 request_code 145 minor_code 7)
> (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'll send another email later regarding my other i386/unstable machine.
Can you please provide a backtrace, because I cannot longer reproduce
the crash. Simply install the following -dbg packages:
libc6-dbg
libgcu-dbg
libglib2.0-0-dbg
libgtk2.0-0-dbg
libgl1-mesa-glx-dbg
libx11-6-dbg
and maybe:
libgoffice-0-4-dbg
libxml2-dbg
and then run gdb (set logging on). To set a breakpoint at gdk_x_error()
follow the information at http://wiki.debian.org/HowToGetABacktrace
(last item). Then please attach the backtrace to your report.
Regards, Daniel
More information about the Debichem-devel
mailing list