Bug 600726

Summary: [abrt] crash in kdebase-runtime-4.4.3-1.fc13.1: Process /usr/bin/nepomukservicestub was killed by signal 6 (SIGABRT)
Product: [Fedora] Fedora Reporter: Kornienko Sergey <vinnitrash>
Component: kdebase-runtimeAssignee: Than Ngo <than>
Status: CLOSED INSUFFICIENT_DATA 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:1a589994558a6e99918738d1b536556b2636bed4
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-07-16 07:37:01 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 Kornienko Sergey 2010-06-05 18:47:12 UTC 
abrt 1.1.0 detected a crash.

architecture: x86_64
Attached file: backtrace
cmdline: /usr/bin/nepomukservicestub nepomukstorage
component: kdebase-runtime
executable: /usr/bin/nepomukservicestub
global_uuid: 1a589994558a6e99918738d1b536556b2636bed4
kernel: 2.6.33.4-95.fc13.x86_64
package: kdebase-runtime-4.4.3-1.fc13.1
rating: 4
reason: Process /usr/bin/nepomukservicestub was killed by signal 6 (SIGABRT)
release: Fedora release 13 (Goddard)
Comment 1 Kornienko Sergey 2010-06-05 18:47:14 UTC 
Created attachment 421479 [details]
File: backtrace
Comment 2 Steven M. Parrish 2010-06-22 00:17:03 UTC 
KDE Version 4.4.4 is now available.  Please update to the this latest release and retest the application.  Please advise if you are still having the same issue as documented.  Any reports not updated within 30 days will be closed.

Thanks from the Fedora KDE Team
Comment 3 Radek Novacek 2010-07-16 07:37:01 UTC 
This backtrace seems not useful at all. Please update abrt and KDE to most
recent versions and try to reproduce this bug. If the problem reoccurs reopen
this bug or open new bug. Thank you.