Bug 591432 - [abrt] crash in kdebase-runtime-4.4.2-3.fc12: Process /usr/bin/nepomukservicestub was killed by signal 11 (SIGSEGV)
Summary: [abrt] crash in kdebase-runtime-4.4.2-3.fc12: Process /usr/bin/nepomukservice...
Keywords:
Status: CLOSED DUPLICATE of bug 586657
Alias: None
Product: Fedora
Classification: Fedora
Component: kdebase-runtime
Version: 12
Hardware: x86_64
OS: Linux
low
medium
Target Milestone: ---
Assignee: Than Ngo
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:0fa1ba2e88a294910a6be9fa0b4...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-05-12 08:58 UTC by Dominique MAGNE
Modified: 2010-05-25 09:43 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-05-25 09:43:06 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)
File: backtrace (29.05 KB, text/plain)
2010-05-12 08:58 UTC, Dominique MAGNE 		no flags Details
View All

Description Dominique MAGNE 2010-05-12 08:58:52 UTC 
abrt 1.0.9 detected a crash.

architecture: x86_64
Attached file: backtrace
cmdline: /usr/bin/nepomukservicestub nepomukstrigiservice
comment: dans le bureau KDE, activer le processus d'indexation des fichiers (nepomuk)  partir de l'outil de configuration du systme KDE
component: kdebase-runtime
executable: /usr/bin/nepomukservicestub
global_uuid: 0fa1ba2e88a294910a6be9fa0b4bc1873c30044f
kernel: 2.6.32.11-99.fc12.x86_64
package: kdebase-runtime-4.4.2-3.fc12
rating: 3
reason: Process /usr/bin/nepomukservicestub was killed by signal 11 (SIGSEGV)
release: Fedora release 12 (Constantine)

How to reproduce
-----
1. dans le bureau KDE, activer le processus d'indexation des fichiers (nepomuk)
2.
3.
Comment 1 Dominique MAGNE 2010-05-12 08:58:55 UTC 
Created attachment 413364 [details]
File: backtrace
Comment 2 Karel Klíč 2010-05-25 09:43:06 UTC 

*** This bug has been marked as a duplicate of bug 586657 ***
Comment 3 Karel Klíč 2010-05-25 09:43:06 UTC 
This bug appears to have been filled using a buggy version of ABRT, because
it contains a backtrace which is a duplicate of backtrace from bug #586657.

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