Version: 2.18.3

What were you doing when the application crashed?
Search for a file in a mount windows share


Distribution: Fedora release 7 (Moonshine)
Gnome Release: 2.18.3 2007-07-02 (Red Hat, Inc)
BugBuddy Version: 2.18.0

System: Linux 2.6.22.4-65.fc7 #1 SMP Tue Aug 21 22:36:56 EDT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 94089216 vsize: 94089216 resident: 31211520 share: 18726912 rss: 31211520 rss_rlim: 4294967295
CPU usage: start_time: 1188899078 rtime: 200 utime: 178 stime: 22 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/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1208809760 (LWP 3704)]
[New Thread -1221399664 (LWP 3733)]
(no debugging symbols found)
0x00110402 in __kernel_vsyscall ()

+ Trace 160342

----------- .xsession-errors (7 sec old) ---------------------
CALLBACK: full-authentication!!!
Window manager warning: Received a _NET_WM_MOVERESIZE message for 0x10019b8 (hda2 on 19); these messages lack timestamps and therefore suck.
--- Hash table keys for warning below:
--> file:///root
(nautilus:3660): Eel-WARNING **: "nautilus-directory.c: directories" hash table still has 1 element at quit time (keys above)
(nautilus:2909): GLib-CRITICAL **: g_utf8_strdown: assertion `str != NULL' failed
Xlib: unexpected async reply (sequence 0x16d5d)!
Initializing nautilus-search-tool extension
Initializing nautilus-open-terminal extension
(nautilus:3704): GLib-CRITICAL **: g_utf8_strdown: assertion `str != NULL' failed
Xlib: unexpected async reply (sequence 0x369a)!
--------------------------------------------------