Bug 605983 - [abrt] crash in kdebase-runtime-4.4.4-1.fc13: raise: Process /usr/bin/nepomukservicestub was killed by signal 6 (SIGABRT)
Summary: [abrt] crash in kdebase-runtime-4.4.4-1.fc13: raise: Process /usr/bin/nepomuk...
Keywords:
Status: CLOSED DUPLICATE of bug 606681
Alias: None
Product: Fedora
Classification: Fedora
Component: kdebase-runtime
Version: 13
Hardware: x86_64
OS: Linux
low
medium
Target Milestone: ---
Assignee: Than Ngo
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:085dca82ba0fee7c48518237d5b...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-06-19 19:05 UTC by Mark T. Kennedy
Modified: 2010-07-13 06:57 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-07-13 06:57:03 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)
File: backtrace (23.23 KB, text/plain)
2010-06-19 19:05 UTC, Mark T. Kennedy 		no flags Details
View All

Description Mark T. Kennedy 2010-06-19 19:05:07 UTC 
abrt 1.1.1 detected a crash.

architecture: x86_64
Attached file: backtrace
cmdline: /usr/bin/nepomukservicestub nepomukstrigiservice
component: kdebase-runtime
crash_function: raise
executable: /usr/bin/nepomukservicestub
global_uuid: 085dca82ba0fee7c48518237d5bc32e32777318f
kernel: 2.6.33.5-124.fc13.x86_64
package: kdebase-runtime-4.4.4-1.fc13
rating: 4
reason: Process /usr/bin/nepomukservicestub was killed by signal 6 (SIGABRT)
release: Fedora release 13 (Goddard)

How to reproduce
-----
1. just boot!
2.
3.
Comment 1 Mark T. Kennedy 2010-06-19 19:05:09 UTC 
Created attachment 425372 [details]
File: backtrace
Comment 2 Steven M. Parrish 2010-06-22 00:16:49 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-13 06:57:03 UTC 

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