GNOME Bugzilla – Bug 505810
crash in Open Folder:
Last modified: 2007-12-27 00:55:08 UTC
Version: 2.18.3 What were you doing when the application crashed? Distribution: Fedora release 7 (Moonshine) Gnome Release: 2.18.3 2007-11-13 (Red Hat, Inc) BugBuddy Version: 2.18.0 System: Linux 2.6.23.1-21.fc7 #1 SMP Thu Nov 1 21:09:24 EDT 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: HighContrastInverse Icon Theme: HighContrastInverse Memory status: size: 59957248 vsize: 59957248 resident: 23175168 share: 19329024 rss: 23175168 rss_rlim: 4294967295 CPU usage: start_time: 1198708612 rtime: 24 utime: 21 stime: 3 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 -1208793376 (LWP 3734)] (no debugging symbols found) 0x00110402 in __kernel_vsyscall ()
+ Trace 183156
Thread 1 (Thread -1208793376 (LWP 3734))
----------- .xsession-errors (12 sec old) --------------------- (avant-window-navigator:3019): Gtk-CRITICAL **: gtk_widget_queue_draw: assertion `GTK_IS_WIDGET (widget)' failed (gnome-session:2733): Gdk-WARNING **: gdk_xsettings_watch_cb(): Couldn't find window to unwatch sh: acpi: command not found /usr/lib/awn/applets/battery-applet/battery-applet.py:131: Warning: g_object_unref: assertion `object->ref_count > 0' failed self.set_temp_icon(icon) (bug-buddy:3686): GLib-GObject-WARNING **: invalid uninstantiatable type `GParamChar' in cast to `GObject' (bug-buddy:3686): GLib-GObject-CRITICAL **: g_object_get_data: assertion `G_IS_OBJECT (object)' failed (bug-buddy:3686): GLib-CRITICAL **: g_hash_table_destroy: assertion `hash_table->ref_count > 0' failed (bug-buddy:3686): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed --------------------------------------------------
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 439977 ***