Bug 592058 - [abrt] crash in tracker-0.6.96-3.fc12: IA__g_str_hash: Process /usr/libexec/trackerd was killed by signal 11 (SIGSEGV)
Summary: [abrt] crash in tracker-0.6.96-3.fc12: IA__g_str_hash: Process /usr/libexec/t...
Keywords:
Status: CLOSED DUPLICATE of bug 571269
Alias: None
Product: Fedora
Classification: Fedora
Component: tracker
Version: 12
Hardware: i686
OS: Linux
low
medium
Target Milestone: ---
Assignee: Deji Akingunola
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:e376e08637663b8a8c7ce4f226e...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-05-13 18:53 UTC by Daniel Demus
Modified: 2010-05-25 10:34 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-05-25 10:34:48 UTC
Type: ---


Attachments (Terms of Use)
File: backtrace (30.56 KB, text/plain)
2010-05-13 18:53 UTC, Daniel Demus
no flags Details

Description Daniel Demus 2010-05-13 18:53:36 UTC
abrt 1.0.9 detected a crash.

architecture: i686
Attached file: backtrace
cmdline: /usr/libexec/trackerd
comment: Trackerd running in the background while rpmbuild was running find-provides
component: tracker
crash_function: IA__g_str_hash
executable: /usr/libexec/trackerd
global_uuid: e376e08637663b8a8c7ce4f226e53fe328eac926
kernel: 2.6.32.11-99.fc12.i686.PAE
package: tracker-0.6.96-3.fc12
rating: 4
reason: Process /usr/libexec/trackerd was killed by signal 11 (SIGSEGV)
release: Fedora release 12 (Constantine)

How to reproduce
-----
1. Let trackerd start indexing in the background
2. Start building an rpm
3.

Comment 1 Daniel Demus 2010-05-13 18:53:38 UTC
Created attachment 413860 [details]
File: backtrace

Comment 2 Karel Klíč 2010-05-25 10:34:48 UTC

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

Comment 3 Karel Klíč 2010-05-25 10:34:48 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 #571269.

Sorry for the inconvenience.


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