Bug 674487

Summary: [abrt] ibus-chewing-1.3.9.2-1.fc14: __memmove_ssse3: Process /usr/libexec/ibus-engine-chewing was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: Chen_Min_Chin <tcfxfzoi>
Component: ibus-chewingAssignee: Ding-Yi Chen <dchen>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 14CC: dchen, i18n-bugs, shawn.p.huang, tagoh
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:d1df974c507dd243b4dfbc146d1657107db5b90f
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-12-05 23:16:24 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
File: backtrace none

Description Chen_Min_Chin 2011-02-02 06:19:22 UTC 
abrt version: 1.1.14
architecture: x86_64
Attached file: backtrace
cmdline: /usr/libexec/ibus-engine-chewing --ibus
component: ibus-chewing
crash_function: __memmove_ssse3
executable: /usr/libexec/ibus-engine-chewing
kernel: 2.6.35.10-74.fc14.x86_64
package: ibus-chewing-1.3.9.2-1.fc14
rating: 4
reason: Process /usr/libexec/ibus-engine-chewing was killed by signal 11 (SIGSEGV)
release: Fedora release 14 (Laughlin)
time: 1296626425
uid: 500

How to reproduce
-----
1.Type chinese
2.The error occur
3.
Comment 1 Chen_Min_Chin 2011-02-02 06:19:47 UTC 
Created attachment 476521 [details]
File: backtrace
Comment 2 Ding-Yi Chen 2011-05-30 06:55:55 UTC 
*** Bug 644850 has been marked as a duplicate of this bug. ***
Comment 3 Ding-Yi Chen 2011-05-30 06:59:34 UTC 
*** Bug 637859 has been marked as a duplicate of this bug. ***
Comment 4 Ding-Yi Chen 2011-05-30 07:08:50 UTC 
Hi, I cannot reproduce this bug on my F14-i386 and RHEL6 x86-64.

Would you mind giving me
1) gconftool-2 -a /desktop/ibus/engine/Chewing
2) uname -a


and possibly the steps to cause the SIGSEGV.

Your understanding is appreciated.
Comment 5 Akira TAGOH 2011-12-05 11:10:12 UTC 
Any updates?
Comment 6 Ding-Yi Chen 2011-12-05 23:16:24 UTC 

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