Bug 636897 - [abrt] tracker-0.8.16-1.fc13: magazine_chain_pop_head: Process /usr/libexec/tracker-miner-fs was killed by signal 11 (SIGSEGV)
Summary: [abrt] tracker-0.8.16-1.fc13: magazine_chain_pop_head: Process /usr/libexec/t...
Keywords:
Status: CLOSED DUPLICATE of bug 589602
Alias: None
Product: Fedora
Classification: Fedora
Component: tracker
Version: 13
Hardware: i686
OS: Linux
low
medium
Target Milestone: ---
Assignee: Deji Akingunola
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:9565a719c51d5a743ed77a1dd2f...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-09-23 15:57 UTC by Alfredo Pons Menargues
Modified: 2010-11-09 14:53 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-11-09 14:53:48 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: backtrace (37.11 KB, text/plain)
2010-09-23 15:57 UTC, Alfredo Pons Menargues
no flags Details

Description Alfredo Pons Menargues 2010-09-23 15:57:15 UTC
abrt version: 1.1.13
architecture: i686
Attached file: backtrace
cmdline: /usr/libexec/tracker-miner-fs
component: tracker
crash_function: magazine_chain_pop_head
executable: /usr/libexec/tracker-miner-fs
kernel: 2.6.33.8-149.fc13.i686
package: tracker-0.8.16-1.fc13
rating: 4
reason: Process /usr/libexec/tracker-miner-fs was killed by signal 11 (SIGSEGV)
release: Fedora release 13 (Goddard)
time: 1285257051
uid: 500

Comment 1 Alfredo Pons Menargues 2010-09-23 15:57:20 UTC
Created attachment 449253 [details]
File: backtrace

Comment 2 Alfredo Pons Menargues 2010-09-24 06:11:50 UTC
I connected a pendrive and immediately after the tracker-miner-fs
 crash

Comment 3 Karel Klíč 2010-11-09 14:53:48 UTC

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

Comment 4 Karel Klíč 2010-11-09 14:53: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 #589602.

Sorry for the inconvenience.


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