GNOME Bugzilla – Bug 513539
crash in Home Folder:
Last modified: 2008-02-01 01:12:58 UTC
What were you doing when the application crashed? Distribution: Debian lenny/sid Gnome Release: 2.20.3 2008-01-12 (Debian) BugBuddy Version: 2.20.1 System: Linux 2.6.22-3-686 #1 SMP Mon Nov 12 08:32:57 UTC 2007 i686 X Vendor: The X.Org Foundation X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: Tactile Icon Theme: black-white_2-Style Memory status: size: 70549504 vsize: 70549504 resident: 20561920 share: 14401536 rss: 20561920 rss_rlim: 4294967295 CPU usage: start_time: 1201814413 rtime: 175 utime: 148 stime: 27 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/i686/cmov/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread 0xb6e1d6b0 (LWP 4721)] (no debugging symbols found) 0xffffe410 in __kernel_vsyscall ()
+ Trace 187654
Thread 1 (Thread 0xb6e1d6b0 (LWP 4721))
----------- .xsession-errors --------------------- Warning: more than one line! (gecko:5052): Pango-WARNING **: Invalid UTF-8 string passed to pango_layout_set_text() (gecko:5052): Pango-WARNING **: Invalid UTF-8 string passed to pango_layout_set_text() (gecko:5052): Gtk-WARNING **: Theme directory scalable/places/22 of theme black-white_2-Style has no size field /home/abigor/.themes/Tactile/gtk-2.0/gtkrc:1046: Bilddatei konnte nicht in pixmap_path gefunden werden: »spin_button_up_arrow_prelight.png« /home/abigor/.themes/Tactile/gtk-2.0/gtkrc:1050: Overlay image options specified without filename /home/abigor/.themes/Tactile/gtk-2.0/gtkrc:1056: Bilddatei konnte nicht in pixmap_path gefunden werden: »spin_button_down_arrow_prelight.png« /home/abigor/.themes/Tactile/gtk-2.0/gtkrc:1060: Overlay image options specified without filename (bug-buddy:5305): Gtk-WARNING **: Theme directory scalable/places/22 of theme black-white_2-Style has no size field --------------------------------------------------
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 ***