GNOME Bugzilla – Bug 498881
crash in Open Folder: Opening properties of a ...
Last modified: 2007-11-22 16:47:12 UTC
Version: 2.18.3 What were you doing when the application crashed? Opening properties of a .png file. Distribution: Debian lenny/sid Gnome Release: 2.20.1 2007-10-26 (Debian) BugBuddy Version: 2.20.1 System: Linux 2.6.22-2-686 #1 SMP Fri Aug 31 00:24:01 UTC 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: gnome Memory status: size: 71487488 vsize: 71487488 resident: 22802432 share: 14761984 rss: 22802432 rss_rlim: 4294967295 CPU usage: start_time: 1195665201 rtime: 9027 utime: 8225 stime: 802 cutime:68 cstime: 28 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 0xb6d856b0 (LWP 8668)] (no debugging symbols found) 0xffffe410 in __kernel_vsyscall ()
+ Trace 179193
Thread 1 (Thread 0xb6d856b0 (LWP 8668))
----------- .xsession-errors --------------------- ** Message: volume = 0 ** (nautilus:8668): WARNING **: destroyed file has call_when_ready pending ** Message: drive = 0 ** Message: volume = 0 ** Message: drive = 0 ** Message: volume = 0 ** Message: drive = 0 ** Message: volume = 0 ** (nautilus:8668): WARNING **: destroyed file has call_when_ready pending Window manager warning: Invalid WM_TRANSIENT_FOR window 0x67 specified for 0x2402bbf (File Info ). Gtk-ERROR **: file /tmp/buildd/gtk+2.0-2.12.1/gtk/gtkliststore.c: line 1677 (gtk_list_store_compare_func): assertion failed: (VALID_ITER (&iter_b, list_store)) aborting... --------------------------------------------------
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 is a Debian specific bug, and Debian is working on providing a fix for this problem. *** This bug has been marked as a duplicate of 440988 ***