Bug 613855

Summary: [abrt] crash in kdebase-runtime-4.4.4-1.fc13: raise: Process /usr/bin/nepomukservicestub was killed by signal 6 (SIGABRT)
Product: [Fedora] Fedora Reporter: Tim McKenzie <tjm1983>
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, smparrish, than
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard: abrt_hash:6ae6853bc1ab5fe61e5a1327826cbc9f49b16b05
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-07-13 06:14:33 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 Tim McKenzie 2010-07-13 00:33:41 UTC
abrt 1.1.1 detected a crash.

architecture: x86_64
Attached file: backtrace
cmdline: /usr/bin/nepomukservicestub nepomukstrigiservice
comment: I was checking a signed file using Kleopatra when this crash happened.  Shortly after it happened, I noticed Strigi in the system tray rapidly telling me all the files it was indexing.  When I was installing/updating my debuginfo packages, it suspended indexing a couple of times due to low disk space.
component: kdebase-runtime
crash_function: raise
executable: /usr/bin/nepomukservicestub
global_uuid: 6ae6853bc1ab5fe61e5a1327826cbc9f49b16b05
kernel: 2.6.33.6-147.fc13.x86_64
package: kdebase-runtime-4.4.4-1.fc13
rating: 4
reason: Process /usr/bin/nepomukservicestub was killed by signal 6 (SIGABRT)
release: Fedora release 13 (Goddard)
How to reproduce: Did not try to reproduce

Comment 1 Tim McKenzie 2010-07-13 00:33:44 UTC
Created attachment 431311 [details]
File: backtrace

Comment 2 Radek Novacek 2010-07-13 06:14:33 UTC

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