Version: 2.20.0

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-686 #1 SMP Mon Feb 11 14:37:45 UTC 2008 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10400090
Selinux: No
Accessibility: Disabled
GTK+ Theme: Glossy
Icon Theme: black-white

Memory status: size: 73400320 vsize: 73400320 resident: 23289856 share: 14503936 rss: 23289856 rss_rlim: 4294967295
CPU usage: start_time: 1208784578 rtime: 345 utime: 318 stime: 27 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 0xb6be9720 (LWP 3730)]
0xffffe410 in __kernel_vsyscall ()

+ Trace 195769

----------- .xsession-errors (17 sec old) ---------------------
(nautilus:3537): Eel-WARNING **: "nautilus-directory.c: directories" hash table still has 1 element at quit time (keys above)
Initializing nautilus-open-terminal extension
Initializing gnome-mount extension
seahorse nautilus module initialized
** (nautilus:3730): WARNING **: Hit unhandled case 38 (Service non disponible) in fm_report_error_loading_directory
** (nautilus:3730): WARNING **: Hit unhandled case 38 (Service non disponible) in fm_report_error_loading_directory
connection_message_func(): Callback
CALLBACK: fill-authentication!!!
connection_message_func(): Callback
CALLBACK: fill-authentication!!!
connection_message_func(): Callback
CALLBACK: full-authentication!!!
--------------------------------------------------