Bug 589247
Summary: | [abrt] crash in tracker-0.8.4-1.fc13: Process /usr/libexec/tracker-store was killed by signal 11 (SIGSEGV) | ||||||
---|---|---|---|---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | piio <bugzilla> | ||||
Component: | tracker | Assignee: | Deji Akingunola <dakingun> | ||||
Status: | CLOSED WORKSFORME | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||
Severity: | medium | Docs Contact: | |||||
Priority: | low | ||||||
Version: | 13 | CC: | dakingun | ||||
Target Milestone: | --- | Keywords: | Reopened | ||||
Target Release: | --- | ||||||
Hardware: | i686 | ||||||
OS: | Linux | ||||||
Whiteboard: | abrt_hash:021ff03dc6737a49779f4a1fb2f040426123f6a6 | ||||||
Fixed In Version: | Doc Type: | Bug Fix | |||||
Doc Text: | Story Points: | --- | |||||
Clone Of: | Environment: | ||||||
Last Closed: | 2010-05-06 12:53:02 UTC | Type: | --- | ||||
Regression: | --- | Mount Type: | --- | ||||
Documentation: | --- | CRM: | |||||
Verified Versions: | Category: | --- | |||||
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
Cloudforms Team: | --- | Target Upstream Version: | |||||
Embargoed: | |||||||
Attachments: |
|
Description
piio
2010-05-05 16:13:55 UTC
Created attachment 411665 [details]
File: backtrace
Have you updated from a previous Fedora release? The crash occurred because tracker-store encountered a corrupt database. The journal will be replayed and everything should be fixed after tracker-store is restarted (for instance by logging out and logging in again). *** This bug has been marked as a duplicate of bug 586706 *** Yes, I've update from fc12. But I'm working almost one month in fc13, this bug didn't happens for me before. I saw him today first time, after I installed updates for tracker. May 05 08:38:02 Updated: tracker-0.8.4-1.fc13.i686 May 05 08:38:45 Updated: tracker-search-tool-0.8.4-1.fc13.i686 My previous versions were: Apr 28 07:23:51 Updated: tracker-0.8.3-1.fc13.i686 Apr 28 07:24:46 Updated: tracker-search-tool-0.8.3-1.fc13.i686 Logging out and logging in doesn't resolve the issue. How can I manually remove journal? I'm sorry, this could a different issue. I will report it upstream (and re-open it here). Looks like this bug doesn't happen again. I can't reproduce him, so let's close him. Closed, thanks. |