GNOME Bugzilla – Bug 554196
crash in Computer:
Last modified: 2008-09-29 20:14:24 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-486 #1 Thu May 8 01:29:10 UTC 2008 i686 X Vendor: The X.Org Foundation X Vendor Release: 10400090 Selinux: No Accessibility: Disabled GTK+ Theme: SphereCrystal Icon Theme: SphereCrystal Memory status: size: 81424384 vsize: 81424384 resident: 26968064 share: 16080896 rss: 26968064 rss_rlim: 4294967295 CPU usage: start_time: 1222615592 rtime: 1308 utime: 1246 stime: 62 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 0xb6b5b940 (LWP 5801)] (no debugging symbols found) 0xffffe410 in __kernel_vsyscall ()
+ Trace 207495
Thread 1 (Thread 0xb6b5b940 (LWP 5801))
----------- .xsession-errors (192 sec old) --------------------- CALLBACK: full-authentication!!! ** (nautilus:5801): WARNING **: Hit unhandled case 31 (Opération annulée) in fm_report_error_loading_directory ** (nautilus:5801): WARNING **: Hit unhandled case 46 (Délai d'expiration atteint) in fm_report_error_loading_directory ** (x-session-manager:3920): WARNING **: Host name lookup failure on localhost. connection_message_func(): Callback CALLBACK: fill-authentication!!! connection_message_func(): Callback CALLBACK: fill-authentication!!! ** (nautilus:5801): WARNING **: Hit unhandled case 2 (Erreur générique) in fm_report_error_loading_directory ** (nautilus:5801): WARNING **: Hit unhandled case 2 (Erreur générique) in fm_report_error_loading_directory --------------------------------------------------
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 ***