Bug 626536

Summary: [abrt] kdebase-runtime-4.4.5-1.fc13: raise: Process /usr/bin/nepomukservicestub was killed by signal 6 (SIGABRT)
Product: [Fedora] Fedora Reporter: Eric Blossom <bugzilla>
Component: kdebase-runtimeAssignee: Than Ngo <than>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: 13CC: fedora, jreznik, kevin, ltinkl, rdieter, rnovacek, ry, smparrish, than
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard: abrt_hash:6334e4b73960515ccbce653b7796c885910451c1
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-08-25 09:02:18 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 Flags
File: backtrace none

Description Eric Blossom 2010-08-23 19:10:46 UTC 
abrt version: 1.1.13
architecture: x86_64
Attached file: backtrace
cmdline: /usr/bin/nepomukservicestub nepomukstrigiservice
comment: Sorry that I can't provide more information.
component: kdebase-runtime
crash_function: raise
executable: /usr/bin/nepomukservicestub
kernel: 2.6.33.6-147.2.4.fc13.x86_64
package: kdebase-runtime-4.4.5-1.fc13
rating: 4
reason: Process /usr/bin/nepomukservicestub was killed by signal 6 (SIGABRT)
release: Fedora release 13 (Goddard)
time: 1282534480
uid: 500

How to reproduce
-----
1. It happened when the indexer automatically started running
2. It's happened twice, not sure that I did anything explicity to actual start it running or to provoke the bug.  
FWIW, the system was updated from F12 to F13 using preupdate.
3.
Comment 1 Eric Blossom 2010-08-23 19:10:48 UTC 
Created an attachment (id=440465)
File: backtrace
Comment 2 Radek Novacek 2010-08-25 09:02:18 UTC 

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