Bug 609358

Summary: [abrt] crash in kdebase-runtime-4.4.4-1.fc13: Process /usr/bin/nepomukservicestub was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: C.J.H. <cogre666>
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, smparrish, than
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard: abrt_hash:667a275ea3b123306449a0506cfc37873501bc5f
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-07-16 07:33:22 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 C.J.H. 2010-06-30 04:52:38 UTC 
abrt 1.1.1 detected a crash.

architecture: x86_64
Attached file: backtrace
cmdline: /usr/bin/nepomukservicestub nepomukstrigiservice
comment: As stated in abrt area of "How to reproduce (in a few simple steps), not sure how to reproduce as the only thing that was done was to turn on the computer and login to kde.
component: kdebase-runtime
executable: /usr/bin/nepomukservicestub
global_uuid: 667a275ea3b123306449a0506cfc37873501bc5f
kernel: 2.6.33.5-124.fc13.x86_64
package: kdebase-runtime-4.4.4-1.fc13
rating: 3
reason: Process /usr/bin/nepomukservicestub was killed by signal 11 (SIGSEGV)
release: Fedora release 13 (Goddard)

How to reproduce
-----
1.not sure, as the only thing that was done was to turn on the computer and login to kde.
2.got the crash / abrt msg within a minute of login.
3.
Comment 1 C.J.H. 2010-06-30 04:52:41 UTC 
Created attachment 427858 [details]
File: backtrace
Comment 2 Radek Novacek 2010-07-16 07:33:22 UTC 

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