Bug 602581

Summary: [abrt] crash in kdebase-runtime-4.4.3-1.fc13.1: memcpy: Process /usr/bin/nepomukservicestub was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: Arthur Pemberton <pembo13>
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, rnovacek, smparrish, thanosk, than
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard: abrt_hash:105cc392101ac0729196286e8011c911507270cf
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-07-15 12:07:58 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 Arthur Pemberton 2010-06-10 08:53:04 UTC 
abrt 1.1.1 detected a crash.

architecture: x86_64
Attached file: backtrace
cmdline: /usr/bin/nepomukservicestub nepomukstrigiservice
component: kdebase-runtime
crash_function: memcpy
executable: /usr/bin/nepomukservicestub
global_uuid: 105cc392101ac0729196286e8011c911507270cf
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 11 (SIGSEGV)
release: Fedora release 13 (Goddard)
Comment 1 Arthur Pemberton 2010-06-10 08:53:07 UTC 
Created attachment 422827 [details]
File: backtrace
Comment 2 Steven M. Parrish 2010-06-22 00:16:43 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-14 09:39:10 UTC 
*** Bug 608839 has been marked as a duplicate of this bug. ***
Comment 4 Radek Novacek 2010-07-15 12:07:58 UTC 

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