GNOME Bugzilla – Bug 530837
crash in Open Folder:
Last modified: 2008-05-01 12:48:30 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.23.9 #1 PREEMPT Thu Dec 6 20:09:36 EST 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: 78913536 vsize: 78913536 resident: 30552064 share: 16592896 rss: 30552064 rss_rlim: 4294967295 CPU usage: start_time: 1209609255 rtime: 203 utime: 188 stime: 15 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 0xb6c11720 (LWP 3831)] (no debugging symbols found) 0xb7625f91 in waitpid () from /lib/libpthread.so.0
+ Trace 196570
Thread 1 (Thread 0xb6c11720 (LWP 3831))
----------- .xsession-errors (18 sec old) --------------------- ** (nautilus:3728): WARNING **: No description found for mime type "x-directory/smb-share" (file is "video"), please tell the gnome-vfs mailing list. (totem:3766): GStreamer-CRITICAL **: gst_object_unref: assertion `object != NULL' failed (totem:3766): GStreamer-CRITICAL **: gst_object_unref: assertion `object != NULL' failed DMO dll supports VO Optimizations 0 1 DMO dll might use previous sample when requested Total Unfree 60 bytes cnt 1 [(nil),0] Initializing gnome-mount extension seahorse nautilus module initialized ** (nautilus:3793): WARNING **: No description found for mime type "x-directory/smb-share" (file is "backup"), please tell the gnome-vfs mailing list. 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 ***