GNOME Bugzilla – Bug 510405
crash in Home Folder: Datei 253SEG1-3 mit Open...
Last modified: 2008-01-18 15:34:09 UTC
What were you doing when the application crashed? Datei 253SEG1-3 mit Open Org math geöffnet Distribution: Debian lenny/sid Gnome Release: 2.20.2 2007-11-29 (Debian) BugBuddy Version: 2.20.1 System: Linux 2.6.22-3-k7 #1 SMP Mon Nov 12 09:12:50 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: 94658560 vsize: 94658560 resident: 27115520 share: 15228928 rss: 27115520 rss_rlim: 4294967295 CPU usage: start_time: 1200665133 rtime: 2944 utime: 2658 stime: 286 cutime:656 cstime: 464 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/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread 0xb6be16c0 (LWP 3228)] [New Thread 0xb12ecb90 (LWP 3551)] (no debugging symbols found) 0xb75d7321 in waitpid () from /lib/libpthread.so.0
+ Trace 185831
Thread 1 (Thread 0xb6be16c0 (LWP 3228))
----------- .xsession-errors --------------------- (nautilus:3228): libgnomevfs-CRITICAL **: gnome_vfs_mime_type_is_known: assertion `!does_string_contain_caps (mime_type)' failed (nautilus:3228): libgnomevfs-CRITICAL **: gnome_vfs_mime_type_is_known: assertion `!does_string_contain_caps (mime_type)' failed (nautilus:3228): libgnomevfs-CRITICAL **: gnome_vfs_mime_type_is_known: assertion `!does_string_contain_caps (mime_type)' failed (nautilus:3228): libgnomevfs-CRITICAL **: gnome_vfs_mime_type_is_known: assertion `!does_string_contain_caps (mime_type)' failed (nautilus:3228): libgnomevfs-CRITICAL **: gnome_vfs_mime_type_is_known: assertion `!does_string_contain_caps (mime_type)' failed (nautilus:3228): libgnomevfs-CRITICAL **: gnome_vfs_mime_type_is_known: assertion `!does_string_contain_caps (mime_type)' failed Fenstermanager-Warnung:Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x2e0006c (OpenOffice) Fenstermanager-Warnung:meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed. (nautilus:3228): 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 ***