GNOME Bugzilla – Bug 547586
crash in File Browser:
Last modified: 2008-08-13 16:48:25 UTC
Version: 2.20.0 What were you doing when the application crashed? Distribution: Debian lenny/sid Gnome Release: 2.22.3 2008-06-30 (Debian) BugBuddy Version: 2.22.0 System: Linux 2.6.25-2-486 #1 Fri Jun 27 02:39:22 UTC 2008 i686 X Vendor: The X.Org Foundation X Vendor Release: 10402000 Selinux: No Accessibility: Disabled GTK+ Theme: Aurora-looks Icon Theme: Elementary_1.8.1b Memory status: size: 93982720 vsize: 93982720 resident: 27635712 share: 17657856 rss: 27635712 rss_rlim: 4294967295 CPU usage: start_time: 1218629071 rtime: 292 utime: 271 stime: 21 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/nautilus' (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread 0xb6b6e720 (LWP 6663)] (no debugging symbols found) 0xb7311f91 in waitpid () from /lib/libpthread.so.0
+ Trace 205092
Thread 1 (Thread 0xb6b6e720 (LWP 6663))
----------- .xsession-errors --------------------- CALLBACK: fill-authentication!!! connection_message_func(): Callback CALLBACK: fill-authentication!!! ** (nautilus:3478): WARNING **: Non è stata trovata alcuna descrizione per il tipo MIME «x-directory/smb-share» (relativa al file «(D)%20Volume»); avvisare cortesemente la mailing list di gnome-v ** (nautilus:3478): WARNING **: Hit unhandled case 46 (Timeout scaduto) in fm_report_error_loading_directory ** (nautilus:3478): WARNING **: Hit unhandled case 46 (Timeout scaduto) in fm_report_error_loading_directory ** (nautilus:3478): WARNING **: Hit unhandled case 38 (Servizio non disponibile) in fm_report_error_loading_directory seahorse nautilus module initialized Initializing gnome-mount extension ** (nautilus:6663): WARNING **: Non è stata trovata alcuna descrizione per il tipo MIME «x-directory/smb-share» (relativa al file «(D)%20Volume»); avvisare cortesemente la mailing list di gnome-v --------------------------------------------------
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 ***