GNOME Bugzilla – Bug 540939
crash in Open Folder:
Last modified: 2008-06-30 15:31:09 UTC
Version: 2.20.0 What were you doing when the application crashed? Distribution: Debian lenny/sid Gnome Release: 2.22.2 2008-05-29 (Debian) BugBuddy Version: 2.22.0 System: Linux 2.6.24.7-gergi #3 SMP Mon Jun 30 12:20:17 EEST 2008 i686 X Vendor: The X.Org Foundation X Vendor Release: 10400090 Selinux: No Accessibility: Disabled GTK+ Theme: Murrina Deviant Icon Theme: dlg-neu Memory status: size: 85794816 vsize: 85794816 resident: 35037184 share: 16125952 rss: 35037184 rss_rlim: 4294967295 CPU usage: start_time: 1214828421 rtime: 4552 utime: 4222 stime: 330 cutime:0 cstime: 3 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 0xb6b74720 (LWP 8570)] (no debugging symbols found) 0xffffe410 in __kernel_vsyscall ()
+ Trace 201763
Thread 1 (Thread 0xb6b74720 (LWP 8570))
----------- .xsession-errors --------------------- (gecko:9637): GLib-GObject-WARNING **: instance of invalid non-instantiatable type `(null)' (gecko:9637): GLib-GObject-CRITICAL **: g_signal_handler_disconnect: assertion `G_TYPE_CHECK_INSTANCE (instance)' failed (gecko:9637): GLib-GObject-WARNING **: instance of invalid non-instantiatable type `(null)' (gecko:9637): GLib-GObject-CRITICAL **: g_signal_handler_disconnect: assertion `G_TYPE_CHECK_INSTANCE (instance)' failed connection_message_func(): Callback CALLBACK: fill-authentication!!! connection_message_func(): Callback CALLBACK: fill-authentication!!! ** (nautilus:8570): WARNING **: No description found for mime type "x-directory/smb-share" (file is "C%24"), please tell the gnome-vfs mailing list. /home/gergi/.themes/Murrina Deviant/gtk-2.0/gtkrc:56: Murrine configuration option "squaredstyle" is not supported and will be ignored. --------------------------------------------------
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 ***