GNOME Bugzilla – Bug 531530
crash in Open Folder:
Last modified: 2008-05-05 11:11:05 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-686 #1 SMP Thu Mar 27 17:45:04 UTC 2008 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: gnome Memory status: size: 83865600 vsize: 83865600 resident: 29044736 share: 16166912 rss: 29044736 rss_rlim: 4294967295 CPU usage: start_time: 1209984326 rtime: 274 utime: 250 stime: 24 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 0xb6c1b720 (LWP 4351)] (no debugging symbols found) 0xffffe410 in __kernel_vsyscall ()
+ Trace 196924
Thread 1 (Thread 0xb6c1b720 (LWP 4351))
----------- .xsession-errors --------------------- Initializing gnome-mount extension seahorse nautilus module initialized ** (nautilus:4323): WARNING **: No description found for mime type "x-directory/smb-share" (file is "NatkoMjuza"), please tell the gnome-vfs mailing list. Initializing gnome-mount extension seahorse nautilus module initialized /usr/lib/python2.4/site-packages/apt/__init__.py:18: FutureWarning: apt API not stable yet warnings.warn("apt API not stable yet", FutureWarning) current dist not found in meta-release file ** (gnome-panel:4036): WARNING **: Failed to establish a connection with GDM: No such file or directory (synaptic:4424): Gtk-CRITICAL **: gtk_tree_view_unref_tree_helper: assertion `node != NULL' failed ** (nautilus:4351): WARNING **: No description found for mime type "x-directory/smb-share" (file is "NatkoMjuza"), please tell the gnome-vfs mailing list. --------------------------------------------------
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find. *** This bug has been marked as a duplicate of 522534 ***