GNOME Bugzilla – Bug 497424
crash in Home Folder:
Last modified: 2007-11-17 22:51:12 UTC
What were you doing when the application crashed? Distribution: Debian lenny/sid Gnome Release: 2.18.3 2007-07-03 (Debian) BugBuddy Version: 2.18.1 System: Linux 2.6.22-2-k7 #1 SMP Fri Aug 31 01:02:37 UTC 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10400000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: gnome Memory status: size: 105541632 vsize: 105541632 resident: 24342528 share: 14753792 rss: 24342528 rss_rlim: 4294967295 CPU usage: start_time: 1195229322 rtime: 641 utime: 589 stime: 52 cutime:0 cstime: 2 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 0xb6e156b0 (LWP 3994)] (no debugging symbols found) 0xffffe410 in __kernel_vsyscall ()
+ Trace 178163
Thread 1 (Thread 0xb6e156b0 (LWP 3994))
----------- .xsession-errors --------------------- (gecko:5302): Pango-WARNING **: Invalid UTF-8 string passed to pango_layout_set_text() (gecko:5302): Pango-WARNING **: Invalid UTF-8 string passed to pango_layout_set_text() Fenstermanager-Warnung:Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x2a00003 (Evince Dok) Fenstermanager-Warnung:meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed. Fenstermanager-Warnung:Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x2a00003 (Evince Dok) Fenstermanager-Warnung:meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed. ** Message: drive = 0 ** Message: volume = 0 ** Message: drive = 0 ** Message: volume = 0 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... --------------------------------------------------
This bug has been fixed in GNOME. Please ask Debian for updates. Thanks! *** This bug has been marked as a duplicate of 440988 ***