Version: 2.20.0

What were you doing when the application crashed?
Browsing an samba drive, with deep directory structure


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

System: Linux 2.6.22-3-686 #1 SMP Sun Feb 10 20:20:49 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: 81268736 vsize: 81268736 resident: 22921216 share: 15106048 rss: 22921216 rss_rlim: 4294967295
CPU usage: start_time: 1212349980 rtime: 262 utime: 244 stime: 18 cutime:0 cstime: 0 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/i686/cmov/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 0xb6bb6720 (LWP 3534)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 199344

----------- .xsession-errors (30 sec old) ---------------------
Initializing gnome-mount extension
seahorse nautilus module initialized
/usr/lib/python2.5/site-packages/apt/__init__.py:18: FutureWarning: apt API not stable yet
  warnings.warn("apt API not stable yet", FutureWarning)
Window manager warning: last_user_time (3075757104) is greater than comparison timestamp (1170222757).  This most likely represents a buggy client sending inaccurate timestamps in messages such as _NE
Window manager warning: 0x2600003 (Software U) appears to be one of the offending windows with a timestamp of 3075757104.  Working around...
current dist not found in meta-release file
Window manager warning: last_user_time (3075757104) is greater than comparison timestamp (1170227210).  This most likely represents a buggy client sending inaccurate timestamps in messages such as _NE
Window manager warning: 0x2600692 () appears to be one of the offending windows with a timestamp of 3075757104.  Working around...
connection_message_func(): Callback
CALLBACK: fill-authentication!!!
connection_message_func(): Callback
CALLBACK: fill-authentication!!!
connection_message_func(): Callback
CALLBACK: full-authentication!!!
--------------------------------------------------