GNOME Bugzilla – Bug 537347
crash in Computer:
Last modified: 2008-06-09 09:37:31 UTC
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-amd64 #1 SMP Sat May 10 09:28:10 UTC 2008 x86_64 X Vendor: The X.Org Foundation X Vendor Release: 10400090 Selinux: No Accessibility: Disabled GTK+ Theme: Glossy Icon Theme: Gorilla Memory status: size: 470495232 vsize: 470495232 resident: 33939456 share: 18358272 rss: 33939456 rss_rlim: 18446744073709551615 CPU usage: start_time: 1212995140 rtime: 295 utime: 262 stime: 33 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 0x2b395bbd5240 (LWP 4709)] (no debugging symbols found) 0x00002b39550cbedf in waitpid () from /lib/libpthread.so.0
+ Trace 199912
Thread 1 (Thread 0x2b395bbd5240 (LWP 4709))
----------- .xsession-errors (32 sec old) --------------------- ** (nautilus:3640): WARNING **: Hit unhandled case 31 (Opération annulée) in fm_report_error_loading_directory 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!!! connection_message_func(): Callback CALLBACK: save-authentication!!! connection_message_func(): Callback CALLBACK: save-authentication!!! Initializing gnome-mount extension seahorse nautilus module initialized --------------------------------------------------
Thanks for taking the time to report this bug. This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade. *** This bug has been marked as a duplicate of 522534 ***