GNOME Bugzilla – Bug 515103
crash in Open Folder: I'm opening a text file....
Last modified: 2008-02-08 11:17:17 UTC
Version: 2.20.0 What were you doing when the application crashed? I'm opening a text file. This text file don't have a ".txt" extension, so i open using the "open with" tool. [when the system crashes) I guess the problem can be on machine's memory! :D Thanks! 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: Aero-ion3.1 Icon Theme: Snow-Apple Memory status: size: 78680064 vsize: 78680064 resident: 27041792 share: 14557184 rss: 27041792 rss_rlim: 4294967295 CPU usage: start_time: 1202423906 rtime: 3003 utime: 2788 stime: 215 cutime:909 cstime: 149 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 0xb6bac6c0 (LWP 30195)] (no debugging symbols found) 0xb75a9321 in waitpid () from /lib/libpthread.so.0
+ Trace 188478
Thread 1 (Thread 0xb6bac6c0 (LWP 30195))
----------- .xsession-errors (7 sec old) --------------------- (eog:31084): Gtk-WARNING **: Theme directory 48x48/mimetypes of theme Snow-Apple has no size field (eog:31117): Gtk-WARNING **: Theme directory 48x48/mimetypes of theme Snow-Apple has no size field (totem:31244): Gtk-WARNING **: Theme directory 48x48/mimetypes of theme Snow-Apple has no size field kbuildsycoca running... Reusing existing ksycoca (nautilus:30195): Eel-WARNING **: No extension, not implemented yet (bug-buddy:31536): Gtk-WARNING **: Theme directory 48x48/mimetypes of theme Snow-Apple 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 ***