Bug 586012 - [abrt] crash in tracker-0.6.96-4.fc13: Process /usr/libexec/trackerd was killed by signal 11 (SIGSEGV)
Summary: [abrt] crash in tracker-0.6.96-4.fc13: Process /usr/libexec/trackerd was kill...
Status: CLOSED DUPLICATE of bug 581504
Alias: None
Product: Fedora
Classification: Fedora
Component: tracker   
(Show other bugs)
Version: 13
Hardware: x86_64 Linux
Target Milestone: ---
Assignee: Deji Akingunola
QA Contact: Fedora Extras Quality Assurance
Whiteboard: abrt_hash:f7c29b4160f2835af6eb57aa05b...
Depends On:
TreeView+ depends on / blocked
Reported: 2010-04-26 16:06 UTC by Boricua
Modified: 2010-05-25 09:45 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2010-05-25 09:45:38 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
File: backtrace (17.80 KB, text/plain)
2010-04-26 16:06 UTC, Boricua
no flags Details

Description Boricua 2010-04-26 16:06:27 UTC
abrt 1.0.9 detected a crash.

architecture: x86_64
Attached file: backtrace
cmdline: /usr/libexec/trackerd
comment: Nothing in particular. Tracker seemed to be running ok and suddenly crashed.
component: tracker
executable: /usr/libexec/trackerd
global_uuid: f7c29b4160f2835af6eb57aa05bf72f8a3a28c76
package: tracker-0.6.96-4.fc13
rating: 4
reason: Process /usr/libexec/trackerd was killed by signal 11 (SIGSEGV)
release: Fedora release 13 (Goddard)

How to reproduce
1.Just keep tracker running in gnome's system tray.

Comment 1 Boricua 2010-04-26 16:06:29 UTC
Created attachment 409225 [details]
File: backtrace

Comment 2 Karel Klíč 2010-05-25 09:45:38 UTC

*** This bug has been marked as a duplicate of bug 581504 ***

Comment 3 Karel Klíč 2010-05-25 09:45:38 UTC
This bug appears to have been filled using a buggy version of ABRT, because
it contains a backtrace which is a duplicate of backtrace from bug #581504.

Sorry for the inconvenience.

Note You need to log in before you can comment on or make changes to this bug.