Version: 2.22.5.1

What were you doing when the application crashed?



Distribution: Fedora release 9 (Sulphur)
Gnome Release: 2.22.3 2008-07-01 (Red Hat, Inc)
BugBuddy Version: 2.22.0

System: Linux 2.6.27.19-78.2.30.fc9.i686 #1 SMP Tue Feb 24 20:09:23 EST 2009 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10502000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Nodoka
Icon Theme: Fedora

Memory status: size: 66433024 vsize: 66433024 resident: 18796544 share: 12267520 rss: 18796544 rss_rlim: 4294967295
CPU usage: start_time: 1238244535 rtime: 59 utime: 49 stime: 10 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 0xb8093770 (LWP 2910)]
[New Thread 0xb7c23b90 (LWP 2912)]
0x00375416 in __kernel_vsyscall ()

+ Trace 213934

----------- .xsession-errors (6 sec old) ---------------------
  (Details: serial 735 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.)
** (gnome-panel:2775): WARNING **: panel-applet-frame.c:1285: failed to load applet OAFIID:TomboyApplet:
(null)
** (nautilus:2910): WARNING **: Unable to add monitor: Ei tuettu
Reading pinyin phrase lib failed
Loading socket FrontEnd module ...
Starting SCIM as daemon ...
Reading pinyin phrase lib failed
--------------------------------------------------