Bug 598823 - [abrt] crash in kdebase-runtime-4.4.3-1.fc13.1: FlacEndAnalyzer::analyze: Process /usr/bin/nepomukservicestub was killed by signal 8 (SIGFPE)
Summary: [abrt] crash in kdebase-runtime-4.4.3-1.fc13.1: FlacEndAnalyzer::analyze: Pro...
Status: CLOSED DUPLICATE of bug 599131
Alias: None
Product: Fedora
Classification: Fedora
Component: kdebase-runtime   
(Show other bugs)
Version: 13
Hardware: x86_64
OS: Linux
Target Milestone: ---
Assignee: Ngo Than
QA Contact: Fedora Extras Quality Assurance
Whiteboard: abrt_hash:f026a8269d50a457ef97b1a5a90...
Depends On:
TreeView+ depends on / blocked
Reported: 2010-06-02 06:17 UTC by Carl G.
Modified: 2010-06-05 22:09 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2010-06-05 22:09:12 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
File: backtrace (82.05 KB, text/plain)
2010-06-02 06:17 UTC, Carl G.
no flags Details

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
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

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

Comment 3 Carl G. 2010-06-05 22:09:12 UTC

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

Note You need to log in before you can comment on or make changes to this bug.