GNOME Bugzilla – Bug 509725
crash in File Browser: I've tried to look the p...
Last modified: 2008-01-15 22:15:14 UTC
Version: 2.18.3 What were you doing when the application crashed? I've tried to look the properties of a folder in a removable h-d (Packard Bell, 160 Gb, dun know the exact model) Distribution: Debian lenny/sid Gnome Release: 2.20.2 2007-11-29 (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: SphereCrystal Icon Theme: Noia Memory status: size: 140439552 vsize: 140439552 resident: 27934720 share: 16199680 rss: 27934720 rss_rlim: 4294967295 CPU usage: start_time: 1200425489 rtime: 240 utime: 225 stime: 15 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 0xb6e126b0 (LWP 10418)] (no debugging symbols found) 0xffffe410 in __kernel_vsyscall ()
+ Trace 185468
Thread 1 (Thread 0xb6e126b0 (LWP 10418))
----------- .xsession-errors (5622 sec old) --------------------- Set Quest: [White Owlie>> ID[624] Type[1] Set Quest: [Revenge>> ID[625] Type[1] Set Quest: [Pursue of the Wolf>> ID[626] Type[1] Set Quest: [Cruel Massacre>> ID[627] Type[1] Set Quest: [Boxing Trouble>> ID[628] Type[1] Set Quest: [Lucky Magical Stone>> ID[629] Type[1] Set Quest: [Investigation of Slowpoke Snail>> ID[630] Type[1] Set Quest: [The Slowpoke Snails>> ID[631] Type[1] Set Quest: [Fallen>> ID[632] Type[1] Set Quest: [Song of the Stinging Beak>> ID[633] Type[1] Set Quest: [Mysterious Cape>> ID[634] Type[1] Set Quest: [Trading Fake Gems>> ID[635] Type[1] Set Quest: [Emerald Fog>> ID[636] Type[1] Set Quest: [Search for Velvet Ston ...Too much output, ignoring rest... --------------------------------------------------
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 ***