Bug 697771

Summary: ibus-m17n sinhala wijesekera crash
Product: [Fedora] Fedora Reporter: Priyadarshana <priyap2222>
Component: ibus-m17nAssignee: Daiki Ueno <dueno>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 14CC: danishka, dcantrell, dueno, i18n-bugs, shawn.p.huang, tfujiwar
Target Milestone: ---   
Target Release: ---   
Hardware: i386   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-04-25 01:49:22 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Priyadarshana 2011-04-19 08:18:52 UTC 
Description of problem:
Actually i am a new user for fedora (Hanthana 14.5) when i chenge my input method as sinhala suddnly it crashed and produce that report.

Version-Release number of selected component (if applicable):
ibus-1.3.9-2.fc14

How reproducible:
i am a novice

Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:
Comment 1 fujiwara 2011-04-20 02:02:59 UTC 
I could not reproduce your problem
If the report was generated by abort, I think it also can attach the stack trace.
Would you attach the trace when you get the crash?
Which application did you use?
Which key sequences did you type?

Also I wonder if you use the latest ibus-m17n
# yum install ibus-m17n
$ rpm -q ibus-m17n
ibus-m17n-1.3.2-1.fc14.x86_64
Comment 2 fujiwara 2011-04-20 02:04:22 UTC 
I guess you use sinhala wijesekera (m17n).
Comment 3 fujiwara 2011-04-25 01:37:30 UTC 
I guess this might be duplicated of bug 696476.
Comment 4 Daiki Ueno 2011-04-25 01:49:22 UTC 
Thanks for forwarding this.  I received quite similar backtrace as bug 696476 from the reporter via Danishka (Hanthana maintainer, Cc'ed).

Closing this for now as duplicate.  If this is not the case, please reopen.

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