What were you doing when the application crashed?
snapshot a window


Distribution: Gentoo Base System release 2.0.1
Gnome Release: 2.31.2 2010-08-23 (Gentoo)
BugBuddy Version: 2.31.3

System: Linux 2.6.35-ccs-r3 #1 SMP Sun Aug 22 09:57:10 CST 2010 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10900000
Selinux: No
Accessibility: Enabled
GTK+ Theme: Clearlooks
Icon Theme: gnome
GTK+ Modules: canberra-gtk-module, gail-gnome, gnomesegvhandler, gnomebreakpad, gail:atk-bridge

Memory status: size: 330477568 vsize: 330477568 resident: 19656704 share: 15802368 rss: 19656704 rss_rlim: 18446744073709551615
CPU usage: start_time: 1282750171 rtime: 58 utime: 50 stime: 8 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

Backtrace was generated from '/usr/bin/gnome-screenshot'

[Thread debugging using libthread_db enabled]
[New Thread 0x7f17f71c3710 (LWP 2931)]
Traceback (most recent call last):
  File "/usr/share/gdb/auto-load/usr/lib64/gcc/x86_64-pc-linux-gnu/4.5.1/libstdc++.so.6.0.14-gdb.py", line 59, in <module>
    from libstdcxx.v6.printers import register_libstdcxx_printers
ImportError: No module named libstdcxx.v6.printers
0x00007f18049649bd in waitpid () from /lib/libpthread.so.0

+ Trace 223396

A debugging session is active.

	Inferior 1 [process 2930] will be detached.

Quit anyway? (y or n) [answered Y; input not from terminal]


---- Critical and fatal warnings logged during execution ----

** Gdk **: The program 'gnome-screenshot' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadWindow (invalid Window parameter)'.
  (Details: serial 3643 error_code 3 request_code 15 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.)