GNOME Bugzilla – Bug 533451
crash in File Browser: Selecting a program to o...
Last modified: 2008-05-17 10:11:40 UTC
Version: 2.20.0 What were you doing when the application crashed? Selecting a program to open a TODO file Distribution: Debian lenny/sid Gnome Release: 2.22.1 2008-04-08 (Debian) BugBuddy Version: 2.22.0 System: Linux 2.6.25-1-686 #1 SMP Mon Apr 28 13:54:58 UTC 2008 i686 X Vendor: The X.Org Foundation X Vendor Release: 10400090 Selinux: No Accessibility: Enabled GTK+ Theme: nimbus Icon Theme: Lynx-Green Memory status: size: 96960512 vsize: 96960512 resident: 40345600 share: 19668992 rss: 40345600 rss_rlim: 4294967295 CPU usage: start_time: 1210917799 rtime: 2561 utime: 2219 stime: 342 cutime:252 cstime: 44 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 0xb6bd5720 (LWP 2998)] [New Thread 0xb48feb90 (LWP 6689)] (no debugging symbols found) 0xb7f88424 in __kernel_vsyscall ()
+ Trace 197900
Thread 1 (Thread 0xb6bd5720 (LWP 2998))
----------- .xsession-errors --------------------- (gecko:6396): GLib-GObject-WARNING **: invalid uninstantiatable type `<invalid>' in cast to `GtkObject' (gecko:6396): GLib-GObject-WARNING **: instance of invalid non-instantiatable type `<invalid>' (gecko:6396): GLib-GObject-CRITICAL **: g_signal_handler_disconnect: assertion `G_TYPE_CHECK_INSTANCE (instance)' failed (gecko:6396): GLib-GObject-WARNING **: instance of invalid non-instantiatable type `<invalid>' (gecko:6396): GLib-GObject-CRITICAL **: g_signal_handler_disconnect: assertion `G_TYPE_CHECK_INSTANCE (instance)' failed (gecko:6396): Gtk-CRITICAL **: gtk_widget_destroy: assertion `GTK_IS_WIDGET (widget)' failed (nautilus:2998): Eel-WARNING **: No extension, not implemented yet (nautilus:2998): Eel-WARNING **: No extension, not implemented yet --------------------------------------------------
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 355018 ***