Bug 164354

Summary: [httx] xim uses different LE to gtk when no LE for locale
Product: Red Hat Enterprise Linux 4 Reporter: Akira TAGOH <tagoh>
Component: im-sdkAssignee: Jens Petersen <petersen>
Status: CLOSED ERRATA QA Contact:
Severity: low Docs Contact:
Priority: medium    
Version: 4.0CC: eng-i18n-bugs
Target Milestone: ---Keywords: i18n
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: RHBA-2006-0119 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2006-03-07 18:33: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:
Bug Depends On: 139811    
Bug Blocks: 125997, 168429    

Description Akira TAGOH 2005-07-27 07:02:54 UTC 
+++ This bug was initially created as a clone of Bug #139811 +++

Description of problem:
Start an gdm X session in a locale with no associated LE.
Then typically depending of the LEs installed httx will use
a different LE from what iiimgcf uses (I think it falls back
to the default dummy LE).

How reproducible:
every time.

Steps to Reproduce:
0. Start a X session in a locale without an associated LE.
1. Start a gtk app and use iiim.
2. Start a xim app and use iiim.
  
Actual results:
1. default LE (En) is used
2. Canna LE was used.

Expected results:
2. same as (1): default LE.

Additional info:
Perhaps some fallback code should be added to iiimxcf?
Comment 1 Lawrence Lim 2005-09-27 04:00:32 UTC 
Will the fix in im-sdk-12.1.1-11.svn2435 be ported to RHEL4??
Comment 2 Jens Petersen 2005-09-30 02:28:15 UTC 
I don't think this is serious to be worth backporting.
Comment 7 Jens Petersen 2005-11-30 08:29:23 UTC 
A patch has been committed into pkg cvs for rhel4 to address this issue.
Comment 10 Red Hat Bugzilla 2006-03-07 18:33:59 UTC 
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on the solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.

http://rhn.redhat.com/errata/RHBA-2006-0119.html