GNOME Bugzilla – Bug 540307
crash in Computer: Reading a windows smb di...
Last modified: 2008-06-26 12:39:09 UTC
Version: 2.20.0 What were you doing when the application crashed? Reading a windows smb directory shared on the local network Distribution: Debian lenny/sid Gnome Release: 2.22.2 2008-05-29 (Debian) BugBuddy Version: 2.22.0 System: Linux 2.6.25-2-686 #1 SMP Thu Jun 12 16:26:30 UTC 2008 i686 X Vendor: The X.Org Foundation X Vendor Release: 10400090 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: gnome Memory status: size: 81620992 vsize: 81620992 resident: 28270592 share: 17031168 rss: 28270592 rss_rlim: 4294967295 CPU usage: start_time: 1214480623 rtime: 814 utime: 769 stime: 45 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 0xb6ace720 (LWP 4811)] (no debugging symbols found) 0xb7f09424 in __kernel_vsyscall ()
+ Trace 201438
Thread 1 (Thread 0xb6ace720 (LWP 4811))
----------- .xsession-errors (16 sec old) --------------------- ** (nautilus:4811): WARNING **: Aucune description trouvée pour le type MIME « x-directory/smb-share » (le fichier est « ftp_loc »), veuillez avertir la liste de diffusion de gnome-vfs. ** (nautilus:4811): WARNING **: Hit unhandled case 46 (Délai d'expiration atteint) in fm_report_error_loading_directory ** (nautilus:4811): WARNING **: Hit unhandled case 46 (Délai d'expiration atteint) in fm_report_error_loading_directory ** (nautilus:4811): WARNING **: Hit unhandled case 46 (Délai d'expiration atteint) in fm_report_error_loading_directory (network-admin:5708): Gtk-WARNING **: Unknown property: GtkComboBox.items connection_message_func(): Callback CALLBACK: fill-authentication!!! connection_message_func(): Callback CALLBACK: fill-authentication!!! --------------------------------------------------
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 ***