Bug 622387

Summary: [abrt] crash in kdebase-runtime-4.4.5-1.fc12: raise: Process /usr/bin/nepomukservicestub was killed by signal 6 (SIGABRT)
Product: [Fedora] Fedora Reporter: Christopher Antila <christopher>
Component: kdebase-runtimeAssignee: Than Ngo <than>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: 12CC: fedora, jreznik, kevin, ltinkl, rdieter, rnovacek, ry, smparrish, than
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard: abrt_hash:3c830a7b0557645353297b7ba93924639af8c91c
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-08-09 12:24:34 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 Christopher Antila 2010-08-09 07:35:40 UTC 
abrt 1.1.1 detected a crash.

architecture: x86_64
Attached file: backtrace
cmdline: /usr/bin/nepomukservicestub nepomukstrigiservice
comment: This bug is supposed to have been fixed since upstream 4.4.4, and for 2+ months, I thought it was.  I don't know if it's helpful, but nepomuk also seems to leak memory like nobody's business.
component: kdebase-runtime
crash_function: raise
executable: /usr/bin/nepomukservicestub
global_uuid: 3c830a7b0557645353297b7ba93924639af8c91c
kernel: 2.6.32.16-150.fc12.x86_64
package: kdebase-runtime-4.4.5-1.fc12
rating: 4
reason: Process /usr/bin/nepomukservicestub was killed by signal 6 (SIGABRT)
release: Fedora release 12 (Constantine)
How to reproduce: Crash in background.
Comment 1 Christopher Antila 2010-08-09 07:35:43 UTC 
Created attachment 437534 [details]
File: backtrace
Comment 2 Radek Novacek 2010-08-09 12:24:34 UTC 

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