What were you doing when the application crashed?
I was trying to access a folder in my ethernet in a windows machine throught samba.


Distribution: Debian 4.0
Gnome Release: 2.22.0 2008-03-14 (Debian)
BugBuddy Version: 2.22.0

System: Linux 2.6.18-6-686 #1 SMP Sun Feb 10 22:11:31 UTC 2008 i686
X Vendor: The X.Org Foundation
X Vendor Release: 70101000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: gnome

Memory status: size: 82276352 vsize: 82276352 resident: 23056384 share: 15728640 rss: 23056384 rss_rlim: 4294967295
CPU usage: start_time: 1208050188 rtime: 363 utime: 341 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/i686/cmov/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1229551840 (LWP 4422)]
[New Thread -1300399216 (LWP 4540)]
[New Thread -1246753904 (LWP 4472)]
(no debugging symbols found)
0xb7ef8410 in ?? ()

+ Trace 195093

----------- .xsession-errors ---------------------
Initializing gnome-mount extension
seahorse nautilus module initialized
connection_message_func(): Callback
CALLBACK: fill-authentication!!!
connection_message_func(): Callback
CALLBACK: fill-authentication!!!
connection_message_func(): Callback
CALLBACK: full-authentication!!!
** (nautilus:4333): WARNING **: Hit unhandled case 31 (Operação cancelada) in fm_report_error_loading_directory
Failed to read a valid object file image from memory.
Initializing gnome-mount extension
seahorse nautilus module initialized
Aviso do gerenciador de janelas: Received a _NET_WM_MOVERESIZE message for 0x10003de (SATA 3 (E)); these messages lack timestamps and therefore suck.
Failed to read a valid object file image from memory.
--------------------------------------------------