Bug 718626

Summary: [hi_IN][mr_IN][gu_IN] input is not working with Ctrl+Space, no keymap selected at first run
Product: [Fedora] Fedora Reporter: A S Alam <aalam>
Component: hindi-typing-boosterAssignee: Pravin Satpute <psatpute>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 15CC: i18n-bugs, mshao, psatpute, shawn.p.huang, tfujiwar
Target Milestone: ---Keywords: i18n
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: hindi-typing-booster-0.0.1-2.fc15 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-07-12 05:56:05 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
screenshot for ibus with Hindi locale
none
im-settings.log file none

Description A S Alam 2011-07-04 04:05:38 UTC
Created attachment 511106 [details]
screenshot for ibus with Hindi locale

Description of problem:
No input method selected during first run in Hindi (hi_IN) locale after fresh install Fedora 15. Installation and User Interface was in Hindi (gnome 3 fall back session)

Version-Release number of selected component (if applicable):
ibus-1.3.99.20110408-2.fc15.i686
ibus-m17n-1.3.2-1.fc15.i686
m17n-db-1.6.2-3.fc15.noarch
m17n-contrib-1.1.12-5.fc15.noarch

How reproducible:
Every time with fresh install

Steps to Reproduce:
1. fresh install with Hindi locale (can create new user, but not tested)
2. login as user
3. open gedit
4. press Ctrl+Space
  
Actual results:
no Hindi input

Expected results:
Hindi input should work

Additional info:
1)Tamil, Punjabi working with default layout
2) Screen-shot with empty Keyboard layout for Hindi

Comment 1 A S Alam 2011-07-04 04:30:08 UTC
Created attachment 511107 [details]
im-settings.log file

Comment 2 A S Alam 2011-07-04 04:31:20 UTC
rpm -qa|grep ibus
----
ibus-1.3.99.20110408-2.fc15.i686
ibus-anthy-1.2.5-4.fc15.i686
ibus-chewing-1.3.9.2-3.fc15.i686
ibus-gtk2-1.3.99.20110408-2.fc15.i686
ibus-gtk3-1.3.99.20110408-2.fc15.i686
ibus-hangul-1.3.1-1.fc15.i686
ibus-indic-table-1.3.1-2.fc15.noarch
ibus-libs-1.3.99.20110408-2.fc15.i686
ibus-m17n-1.3.2-1.fc15.i686
ibus-pinyin-1.3.99.20110217-2.fc15.i686
ibus-pinyin-db-open-phrase-1.3.99.20110217-2.fc15.noarch
ibus-rawcode-1.3.1.20100707-4.fc15.i686
libusb-0.1.3-7.fc15.i686
libusb1-1.0.8-7.fc15.i686
libuser-0.57.2-1.fc15.i686
libuser-python-0.57.2-1.fc15.i686
----
rpm -qa|grep m17n
----
ibus-m17n-1.3.2-1.fc15.i686
m17n-contrib-1.1.12-5.fc15.noarch
m17n-db-1.6.2-3.fc15.noarch
m17n-lib-1.6.2-3.fc15.i686

Comment 3 fujiwara 2011-07-04 06:06:03 UTC
There are two problems:
One is the language is different between ibus-indic-table and ibus-m17n.

E.g. ibus-indic-table
% /usr/libexec/ibus-engine-indic-table --xml
    <engine>
        <name>hindi-phonetic</name>
        <longname>hindi-phonetic</longname>
        <language>hi_IN</language>
...
        <layout>us</layout>
        <description>This is a Marathi Typing booster engine table for IBus Table.</description>
    </engine>


E.g. ibus-m17n
% /usr/libexec/ibus-engine-m17n --xml
        <engine>
            <name>m17n:hi:phonetic</name>
            <longname>phonetic (m17n)</longname>
            <description>Hindi input method for phonetic layout.
...
            <language>hi</language>
            <rank>1</rank>
        </engine>


The m17n language is hi but indic-table lang is hi_IN.
I'd recommend to have the same language between engines.

If the languages are different, the long name has the higher priority so currently indic-table is checked at first but they are no rank tag above.
So Hindi locale doesn't load any engines by default.
If you uninstall ibus-indic-table, then the short name (hi) is checked and m17n engines are loaded because they has rank 1 above.

If you'd like to load ibus-indic-table engines by default, they needs the non-zero rank in the xml output.

Forwarding to ibus-indic-table at first.

Comment 4 Pravin Satpute 2011-07-04 08:43:37 UTC
thanks fujiwara for analysis.
Yeah, this problem is from ibus-indic-table, i need to fix this in all typing booster ime's

i.e. hindi-typing-booster
tamil-typing-booster
gujarati-typing-booster
marathi-typing-booster


i will finish this today itself

Comment 5 Fedora Update System 2011-07-04 10:04:13 UTC
hindi-typing-booster-0.0.1-2.fc15 has been submitted as an update for Fedora 15.
https://admin.fedoraproject.org/updates/hindi-typing-booster-0.0.1-2.fc15

Comment 6 Fedora Update System 2011-07-04 18:57:57 UTC
Package hindi-typing-booster-0.0.1-2.fc15, gujarati-typing-booster-0.0.1-2.fc15, tamil-typing-booster-0.0.1-2.fc15, marathi-typing-booster-0.0.1-2.fc15:
* should fix your issue,
* was pushed to the Fedora 15 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing hindi-typing-booster-0.0.1-2.fc15 gujarati-typing-booster-0.0.1-2.fc15 tamil-typing-booster-0.0.1-2.fc15 marathi-typing-booster-0.0.1-2.fc15'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/gujarati-typing-booster-0.0.1-2.fc15,tamil-typing-booster-0.0.1-2.fc15,hindi-typing-booster-0.0.1-2.fc15,marathi-typing-booster-0.0.1-2.fc15
then log in and leave karma (feedback).

Comment 7 A S Alam 2011-07-07 06:36:14 UTC
although bug is fixed, but just for Reference, Other Effected languages:
Marathi (mr_IN)
Gujarati (gu_IN)

Comment 8 Fedora Update System 2011-07-12 22:00:54 UTC
hindi-typing-booster-0.0.1-2.fc15, gujarati-typing-booster-0.0.1-2.fc15, tamil-typing-booster-0.0.1-2.fc15, marathi-typing-booster-0.0.1-2.fc15 has been pushed to the Fedora 15 stable repository.  If problems still persist, please make note of it in this bug report.