On Mon, 2009-12-21 at 15:07 -0800, Rob Healey wrote: > Greetings: > > I have been receiving this same error since gtk-2.19.x. i was hoping > that it would get resolved, but then I was thinking, what if no one > else get it? > > Here is my error from the terminal window... > > Gdk-ERROR **: The program 'gramps.py' received an X Window System > error. > This probably reflects a bug in the program. > The error was 'BadWindow (invalid Window parameter)'. > (Details: serial 21699 error_code 3 request_code 20 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.) > aborting... > Trace/breakpoint trap > Do you have a bug open about this yet? Try following the above instructions; and run "t a a bt" in gdb when you hit the breakpoint in gdk_x_error (short for "thread apply all backtrace"). Attach the result to the bug. More info on doing this can be seen at: http://fedoraproject.org/wiki/StackTraces#gdb I've seen a few such errors, and at least one of these turned out to be fallout from the change to client-side windows in gtk-2.18: http://library.gnome.org/devel/gtk/unstable/gtk-migrating-ClientSideWindows.html See e.g. https://bugzilla.redhat.com/show_bug.cgi?id=543278 (istanbul) and possibly: https://bugzilla.redhat.com/show_bug.cgi?id=540810 (virt-manager) and maybe: https://bugzilla.redhat.com/show_bug.cgi?id=546159 (ibus). A good backtrace in bugzilla is the best way to track this down, I think. Hope this is helpful Dave -- fedora-test-list mailing list fedora-test-list@xxxxxxxxxx To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-test-list
