abrt 1.1.1 detected a crash. architecture: x86_64 Attached file: backtrace cmdline: /usr/libexec/tracker-store comment: Well, nothing, was AFK component: tracker crash_function: raise executable: /usr/libexec/tracker-store global_uuid: 61c5e2dd311357b39c8607e1a615906c33392650 kernel: 2.6.33.6-147.2.4.fc13.x86_64 package: tracker-0.8.15-2.fc13 rating: 4 reason: Process /usr/libexec/tracker-store was killed by signal 6 (SIGABRT) release: Fedora release 13 (Goddard) How to reproduce ----- 1. Tracker was indexing 2. 3.
Created attachment 438012 [details] File: backtrace
Is this installation an upgrade from a previous Fedora installation? And is does this happen the first time you tried to use tracker? The crash seems to be caused by a corrupted journal, which is usually recreated the next time you start tracker.
It happens months after a full distro version upgrade. Tracker was started after a new session login and I was AFK.
I believe the issue is due to the incompatibility between tracker-0.8.x and previous tracker-0.6.x database format. tracker-0.8 should fix itself on restart. Closing as NOTABUG, please re-open if similar crash occurs again.