GNOME Bugzilla – Bug 530494
crash in Computer: Try to brows a network s...
Last modified: 2008-04-29 07:12:34 UTC
Version: 2.20.0 What were you doing when the application crashed? Try to brows a network share under nautilus Distribution: Debian lenny/sid Gnome Release: 2.22.1 2008-04-08 (Debian) BugBuddy Version: 2.22.0 System: Linux 2.6.22-3-686 #1 SMP Mon Nov 12 08:32:57 UTC 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: gnome Memory status: size: 80326656 vsize: 80326656 resident: 24887296 share: 15273984 rss: 24887296 rss_rlim: 4294967295 CPU usage: start_time: 1209448519 rtime: 93 utime: 35 stime: 58 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 0xb6b87720 (LWP 2947)] (no debugging symbols found) 0xffffe402 in __kernel_vsyscall ()
+ Trace 196408
Thread 1 (Thread 0xb6b87720 (LWP 2947))
----------- .xsession-errors (10 sec old) --------------------- ** (nautilus:2601): WARNING **: Aucune description trouvée pour le type MIME « x-directory/smb-share » (le fichier est « nas »), veuillez avertir la liste de diffusion de gnome-vfs. 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!!! seahorse nautilus module initialized Initializing gnome-mount extension ** (nautilus:2947): WARNING **: Aucune description trouvée pour le type MIME « x-directory/smb-share » (le fichier est « nas »), veuillez avertir la liste de diffusion de gnome-vfs. --------------------------------------------------
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 ***