Version: 2.20.0

What were you doing when the application crashed?



Distribution: Debian 5.0
Gnome Release: 2.22.3 2008-09-18 (Debian)
BugBuddy Version: 2.22.0

System: Linux 2.6.26-1-amd64 #1 SMP Sat Jan 10 17:57:00 UTC 2009 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10402000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: gnome

Memory status: size: 469229568 vsize: 469229568 resident: 16699392 share: 11968512 rss: 16699392 rss_rlim: 18446744073709551615
CPU usage: start_time: 1234081521 rtime: 14 utime: 10 stime: 4 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

Backtrace was generated from '/usr/bin/nautilus'

[Thread debugging using libthread_db enabled]
[New Thread 0x7f4731030780 (LWP 30340)]
0x00000030da00e5ef in waitpid () from /lib/libpthread.so.0

+ Trace 212343

----------- .xsession-errors ---------------------
The error was 'BadPixmap (invalid Pixmap parameter)'.
  (Details: serial 1011 error_code 4 request_code 55 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.)
Initializing diff-ext
Got Event! 33, -1
Initializing nautilus-image-converter extension
seahorse nautilus module initialized
Initializing gnome-mount extension
Could not find the frame base for "IA__g_spawn_sync".
Could not find the frame base for "IA__g_spawn_sync".
Could not find the frame base for "IA__g_spawn_sync".
--------------------------------------------------