Version: 2.20.0

What were you doing when the application crashed?



Distribution: Debian lenny/sid
Gnome Release: 2.22.0 2008-03-14 (Debian)
BugBuddy Version: 2.22.0

System: Linux 2.6.24-1-686 #1 SMP Thu Mar 27 17:45:04 UTC 2008 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: gnome

Memory status: size: 78323712 vsize: 78323712 resident: 26419200 share: 15777792 rss: 26419200 rss_rlim: 4294967295
CPU usage: start_time: 1212704170 rtime: 43613 utime: 38014 stime: 5599 cutime:0 cstime: 1 timeout: 0 it_real_value: 0 frequency: 100

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

Using host libthread_db library "/lib/i686/cmov/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread 0xb6baa720 (LWP 5337)]
0xffffe410 in __kernel_vsyscall ()

+ Trace 199754

----------- .xsession-errors (54 sec old) ---------------------
Got 256 exact BGR233 colours out of 256
Using BGR233 pixel format:
  8 bits per pixel.
  True colour: max red 7 green 7 blue 3, shift red 0 green 3 blue 6
Using shared memory PutImage
Throughput 7680 kbit/s - changing from 8bit
Using viewer's native pixel format:
  32 bits per pixel.
  Least significant byte first in each pixel.
  True colour: max red 255 green 255 blue 255, shift red 16 green 8 blue 0
Throughput 14209 kbit/s - changing to Hextile
ShmCleanup called
(gnome-terminal:4437): Vte-WARNING **: No handler for control sequence `device-control-string' defined.
Window manager warning: Received a _NET_WM_MOVERESIZE message for 0x12056ee (Windows Ne); these messages lack timestamps and therefore suck.
--------------------------------------------------