GNOME Bugzilla – Bug 523778
crash in Home Folder: after i delete my trash ...
Last modified: 2008-03-22 09:17:40 UTC
What were you doing when the application crashed? after i delete my trash i would like to look a dvd. sorry for my english, but it is not my homrlanguage Distribution: Debian lenny/sid Gnome Release: 2.20.3 2008-01-12 (Debian) BugBuddy Version: 2.20.1 System: Linux 2.6.22-2-486 #1 Thu Aug 30 23:45:36 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: 74862592 vsize: 74862592 resident: 23269376 share: 15568896 rss: 23269376 rss_rlim: 4294967295 CPU usage: start_time: 1206109797 rtime: 1334 utime: 1212 stime: 122 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 0xb6c336c0 (LWP 2812)] (no debugging symbols found) 0xffffe410 in __kernel_vsyscall ()
+ Trace 193041
Thread 1 (Thread 0xb6c336c0 (LWP 2812))
----------- .xsession-errors (16 sec old) --------------------- (gecko:2931): Pango-WARNING **: Invalid UTF-8 string passed to pango_layout_set_text() (gecko:2931): Pango-WARNING **: Invalid UTF-8 string passed to pango_layout_set_text() (gecko:2931): Pango-WARNING **: Invalid UTF-8 string passed to pango_layout_set_text() (gecko:2931): Pango-WARNING **: Invalid UTF-8 string passed to pango_layout_set_text() (gecko:2931): Pango-WARNING **: Invalid UTF-8 string passed to pango_layout_set_text() Fenstermanager-Warnung:Ungültiges WM_TRANSIENT_FOR-Fenster 0x63 festgelegt für 0x10002e4 (). (nautilus:2812): Eel-WARNING **: No extension, not implemented yet (nautilus:2812): Eel-WARNING **: No extension, not implemented yet --------------------------------------------------
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 ***