What were you doing when the application crashed?



Distribution: Debian lenny/sid
Gnome Release: 2.22.1 2008-04-08 (Debian)
BugBuddy Version: 2.22.0

System: Linux 2.6.24-1-amd64 #1 SMP Fri Apr 18 23:08:22 UTC 2008 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Gion

Memory status: size: 458387456 vsize: 458387456 resident: 33869824 share: 14360576 rss: 33869824 rss_rlim: 18446744073709551615
CPU usage: start_time: 1210361221 rtime: 3325 utime: 3006 stime: 319 cutime:22 cstime: 16 timeout: 0 it_real_value: 0 frequency: 100

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

(no debugging symbols found)
Using host libthread_db library "/lib/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 0x2b3426e6fb80 (LWP 7829)]
(no debugging symbols found)
0x00002b3420994edf in waitpid () from /lib/libpthread.so.0

+ Trace 197339

----------- .xsession-errors (141 sec old) ---------------------
Fenstermanager-Warnung:last_user_time (1155146400) is greater than comparison timestamp (3475784139).  This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET
Fenstermanager-Warnung:0x3e0001e (Terminal) appears to be one of the offending windows with a timestamp of 1155146400.  Working around...
cairo context error: NULL pointer
cairo context error: NULL pointer
cairo context error: NULL pointer
connection_message_func(): Callback
CALLBACK: fill-authentication!!!
connection_message_func(): Callback
CALLBACK: fill-authentication!!!
connection_message_func(): Callback
CALLBACK: full-authentication!!!
connection_message_func(): Callback
CALLBACK: save-authentication!!!
connection_message_func(): Callback
CALLBACK: save-authentication!!!
--------------------------------------------------