What were you doing when the application crashed?



Distribution: Debian lenny/sid
Gnome Release: 2.22.3 2008-06-30 (Debian)
BugBuddy Version: 2.22.0

System: Linux 2.6.25-2-686 #1 SMP Fri Jun 27 03:23:20 UTC 2008 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10402000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: gnome

Memory status: size: 96935936 vsize: 96935936 resident: 26181632 share: 16646144 rss: 26181632 rss_rlim: 4294967295
CPU usage: start_time: 1216373202 rtime: 277 utime: 252 stime: 25 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

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

(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 0xb6b5b720 (LWP 4098)]
(no debugging symbols found)
0xb7f8e424 in __kernel_vsyscall ()

+ Trace 203169

----------- .xsession-errors (12 sec old) ---------------------
  (Details: serial 82 error_code 2 request_code 140 minor_code 19)
  (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.)
The program 'totem' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadValue (integer parameter out of range for operation)'.
  (Details: serial 82 error_code 2 request_code 140 minor_code 19)
  (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.)
--------------------------------------------------