GNOME Bugzilla – Bug 564547
crash in Open Folder:
Last modified: 2008-12-15 08:45:08 UTC
Version: 2.20.0 What were you doing when the application crashed? Distribution: Unknown Gnome Release: 2.22.3 2008-06-30 (Debian) BugBuddy Version: 2.22.0 System: Linux 2.6.24.4 #4 SMP PREEMPT Wed Apr 30 09:00:21 PHT 2008 i686 X Vendor: The X.Org Foundation X Vendor Release: 10402000 Selinux: No Accessibility: Disabled GTK+ Theme: Industrial Icon Theme: gnome Memory status: size: 77541376 vsize: 77541376 resident: 25989120 share: 15110144 rss: 25989120 rss_rlim: 4294967295 CPU usage: start_time: 1229308025 rtime: 238 utime: 224 stime: 14 cutime:0 cstime: 0 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 0xb6b99720 (LWP 10069)] (no debugging symbols found) 0xb7fdf410 in __kernel_vsyscall ()
+ Trace 210809
Thread 1 (Thread 0xb6b99720 (LWP 10069))
----------- .xsession-errors (1785 sec old) --------------------- (nautilus:5253): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed (nautilus:5253): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed (nautilus:5253): GdkPixbuf-CRITICAL **: gdk_pixbuf_get_has_alpha: assertion `pixbuf != NULL' failed (nautilus:5253): GLib-GObject-CRITICAL **: g_object_ref: assertion `G_IS_OBJECT (object)' failed (nautilus:5253): GdkPixbuf-CRITICAL **: gdk_pixbuf_get_width: assertion `pixbuf != NULL' failed (nautilus:5253): GdkPixbuf-CRITICAL **: gdk_pixbuf_get_height: assertion `pixbuf != NULL' failed (nautilus:5253): GdkPixbuf-CRITICAL **: gdk_pixbuf_copy_area: assertion `src_pixbuf != NULL' failed ...Too much output, ignoring rest... --------------------------------------------------
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 ***