Bug 598823

Summary: [abrt] crash in kdebase-runtime-4.4.3-1.fc13.1: FlacEndAnalyzer::analyze: Process /usr/bin/nepomukservicestub was killed by signal 8 (SIGFPE)
Product: [Fedora] Fedora Reporter: Carl G. <carlg>
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:f026a8269d50a457ef97b1a5a9003c786cb8c04f
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-06-05 22:09:12 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 Carl G. 2010-06-02 06:17:43 UTC 
abrt 1.1.0 detected a crash.

architecture: x86_64
Attached file: backtrace
cmdline: /usr/bin/nepomukservicestub nepomukstrigiservice
component: kdebase-runtime
crash_function: FlacEndAnalyzer::analyze
executable: /usr/bin/nepomukservicestub
global_uuid: f026a8269d50a457ef97b1a5a9003c786cb8c04f
kernel: 2.6.33.5-112.fc13.x86_64
package: kdebase-runtime-4.4.3-1.fc13.1
rating: 4
reason: Process /usr/bin/nepomukservicestub was killed by signal 8 (SIGFPE)
release: Fedora release 13 (Goddard)
Comment 1 Carl G. 2010-06-02 06:17:46 UTC 
Created attachment 418924 [details]
File: backtrace
Comment 2 Steven M. Parrish 2010-06-05 02:34:13 UTC 
This is a issue which needs to be reported upstream.  Please file a report at
http://bugs.kde.org  

Please add upstream report info to this report.  We will monitor the upstream
report for a resolution.

Thanks for the report



-- 
Fedora Bugzappers volunteer triage team
https://fedoraproject.org/wiki/BugZappers
Comment 3 Carl G. 2010-06-05 22:09:12 UTC 

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