Bug 636910

Summary: [abrt] kdebase-runtime-4.4.5-1.fc13: raise: Process /usr/bin/nepomukservicestub was killed by signal 6 (SIGABRT)
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: jreznik, kevin, ltinkl, rdieter, rnovacek, ry, smparrish, than, thomasj
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard: abrt_hash:69b99b4cc920e3fb7d4fe4555cec641496cfa0ca
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-09-24 11:08: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 C.J.H. 2010-09-23 16:32:41 UTC
abrt version: 1.1.13
architecture: x86_64
Attached file: backtrace
cmdline: /usr/bin/nepomukservicestub nepomukstrigiservice
comment: As I said in the step-by-step...."7.all this means is that it appears to be a completely random crash"...
component: kdebase-runtime
crash_function: raise
executable: /usr/bin/nepomukservicestub
kernel: 2.6.34.7-56.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: 1285258901
uid: 1000

How to reproduce
-----
1.Log in to KDE
2.opened K3B to burn a disc
3.at the start of burning the 2nd disc got the abrt crash/popup happened
4.disc failed to even start to burn
5.closed k3b
6.reopened k3b to attempt to burn disc again=success
7.all this means is that it appears to be a completely random crash

Comment 1 C.J.H. 2010-09-23 16:32:44 UTC
Created attachment 449257 [details]
File: backtrace

Comment 2 Radek Novacek 2010-09-24 11:08:33 UTC

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