GNOME Bugzilla – Bug 641222
crash in Home Folder: I was cleaning up my 'Do...
Last modified: 2011-02-02 08:40:12 UTC
What were you doing when the application crashed? I was cleaning up my 'Downloads' directory, deleting unneeded files. Distribution: Debian 6.0 Gnome Release: 2.30.2 2010-11-12 (Debian) BugBuddy Version: 2.30.0 System: Linux 2.6.32-5-686 #1 SMP Wed Jan 12 04:01:41 UTC 2011 i686 X Vendor: The X.Org Foundation X Vendor Release: 10707000 Selinux: No Accessibility: Disabled GTK+ Theme: Unity Icon Theme: Tango GTK+ Modules: gnomebreakpad, canberra-gtk-module Memory status: size: 150204416 vsize: 150204416 resident: 29548544 share: 20885504 rss: 29548544 rss_rlim: 18446744073709551615 CPU usage: start_time: 1296635592 rtime: 727 utime: 658 stime: 69 cutime:320 cstime: 40 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/nautilus' [Thread debugging using libthread_db enabled] [New Thread 0xaee82b70 (LWP 3533)] 0xb77bb424 in __kernel_vsyscall ()
+ Trace 225809
Thread 1 (Thread 0xb66c9760 (LWP 3349))
Inferior 1 [process 3349] will be detached. Quit anyway? (y or n) [answered Y; input not from terminal] ----------- .xsession-errors (127 sec old) --------------------- Tracker-Message: Readonly mode ........................ no Tracker-Message: Registering D-Bus object... Tracker-Message: Path:'/org/freedesktop/Tracker1/Status' Tracker-Message: Type:'TrackerStatus' Starting log: File:'/home/bvanhaute/.local/share/tracker/tracker-miner-fs.log' Tracker-Message: Setting database locations Tracker-Message: Checking database directories exist Tracker-Message: Checking database version Tracker-Message: Checking database files exist Tracker-Message: Loading databases files... Tracker-Message: Didn't shut down cleanly last time, doing integrity checks Tracker-Message: Loading database... '/home/bvanhaute/.cache/tracker/meta.db' (metadata) Tracker-Message: Opened sqlite3 database:'/home/bvanhaute/.cache/tracker/meta.db' Tracker-Message: Setting cache size to 2000 --------------------------------------------------
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 bug 602500 ***