GNOME Bugzilla – Bug 536817
crash in File Browser:
Last modified: 2008-06-05 17:46:36 UTC
Version: 2.20.0 What were you doing when the application crashed? Distribution: Debian lenny/sid Gnome Release: 2.22.1 2008-04-08 (Debian) BugBuddy Version: 2.22.0 System: Linux 2.6.24-1-686 #1 SMP Thu May 8 02:16:39 UTC 2008 i686 X Vendor: The X.Org Foundation X Vendor Release: 10400090 Selinux: No Accessibility: Disabled GTK+ Theme: Phacile-beige Icon Theme: Mac_OS_X_Leopard_for_Debian_v1.4 Memory status: size: 88195072 vsize: 88195072 resident: 32804864 share: 18378752 rss: 32804864 rss_rlim: 4294967295 CPU usage: start_time: 1212682077 rtime: 3620 utime: 3470 stime: 150 cutime:815 cstime: 37 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 0xb6c2d720 (LWP 3382)] (no debugging symbols found) 0xffffe410 in __kernel_vsyscall ()
+ Trace 199648
Thread 1 (Thread 0xb6c2d720 (LWP 3382))
----------- .xsession-errors --------------------- fixme:icon:DrawIconEx Ignoring istep=16 fixme:icon:DrawIconEx Ignoring istep=16 fixme:icon:DrawIconEx Ignoring istep=16 fixme:icon:DrawIconEx Ignoring istep=16 fixme:icon:DrawIconEx Ignoring istep=16 fixme:icon:DrawIconEx Ignoring istep=16 fixme:icon:DrawIconEx Ignoring istep=16 fixme:icon:DrawIconEx Ignoring istep=16 fixme:icon:DrawIconEx Ignoring istep=16 fixme:icon:DrawIconEx Ignoring istep=16 fixme:shell:SHAutoComplete SHAutoComplete stub fixme:icon:DrawIconEx Ignoring istep=16 fixme:icon:DrawIconEx Ignoring istep=16 (nautilus:3382): 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 ***