Bug 603292 - [abrt] crash in kdebase-runtime-4.4.3-1.fc13.1: ref: Process /usr/bin/nepomukservicestub was killed by signal 11 (SIGSEGV)
Summary: [abrt] crash in kdebase-runtime-4.4.3-1.fc13.1: ref: Process /usr/bin/nepomuk...
Keywords:
Status: CLOSED DUPLICATE of bug 576514
Alias: None
Product: Fedora
Classification: Fedora
Component: kdebase-runtime
Version: 13
Hardware: i686
OS: Linux
low
medium
Target Milestone: ---
Assignee: Than Ngo
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:6489bfb4f327e612751f23dbf3d...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-06-12 08:03 UTC by Mustafa Hasan TUNCER
Modified: 2010-07-16 06:52 UTC (History)
7 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2010-07-16 06:52:36 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)
File: backtrace (23.47 KB, text/plain)
2010-06-12 08:03 UTC, Mustafa Hasan TUNCER 		no flags Details
View All

Description Mustafa Hasan TUNCER 2010-06-12 08:03:21 UTC 
abrt 1.1.1 detected a crash.

architecture: i686
Attached file: backtrace
cmdline: /usr/bin/nepomukservicestub nepomukstorage
component: kdebase-runtime
crash_function: ref
executable: /usr/bin/nepomukservicestub
global_uuid: 6489bfb4f327e612751f23dbf3d39197f3df6ee9
kernel: 2.6.33.5-112.fc13.i686.PAE
package: kdebase-runtime-4.4.3-1.fc13.1
rating: 4
reason: Process /usr/bin/nepomukservicestub was killed by signal 11 (SIGSEGV)
release: Fedora release 13 (Goddard)

How to reproduce
-----
1.I have just started the Kmail!
2.
3.
Comment 1 Mustafa Hasan TUNCER 2010-06-12 08:03:24 UTC 
Created attachment 423458 [details]
File: backtrace
Comment 2 Steven M. Parrish 2010-06-22 00:17:07 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 06:52:36 UTC 

*** This bug has been marked as a duplicate of bug 576514 ***
Note You need to log in before you can comment on or make changes to this bug.