Avro Bengali keyboard switches to Malay (Jawi) after upgrade to Ubuntu 17.04

The name of the pictureThe name of the pictureThe name of the pictureClash Royale CLAN TAG#URR8PPP








up vote
6
down vote

favorite
1












I upgraded one of my machines to Ubuntu 17.04. May be it is related, may be it is not, but for this machine, Avro Bengali keyboard switched to Malay (Jawi) after upgrade.



My other two machines, running Ubuntu 16.04 are working fine.



Please see these self explanatory screenshots.



enter image description here



enter image description here



I tried removing and re-adding the keyboard, uninstalling and reinstalling the keyboard without any avail.



Whenever, I switch to Avro keyboard, I get texts in Arabic.










share|improve this question























  • I installed the thing on my 16.10, and I don't get a keyboard layout chart at all... One thing you may want to do is to install the ibus-m17n package and try the Bengali options provided by that package.
    – Gunnar Hjalmarsson
    Apr 12 '17 at 14:16






  • 1




    Same issue. It was working on 16.10 but not working on 17.04
    – Pavak Paul
    Apr 14 '17 at 13:09










  • @GunnarHjalmarsson I installed ibus-m17n, no improvement. Thanks anyway.
    – Masroor
    Apr 15 '17 at 7:27














up vote
6
down vote

favorite
1












I upgraded one of my machines to Ubuntu 17.04. May be it is related, may be it is not, but for this machine, Avro Bengali keyboard switched to Malay (Jawi) after upgrade.



My other two machines, running Ubuntu 16.04 are working fine.



Please see these self explanatory screenshots.



enter image description here



enter image description here



I tried removing and re-adding the keyboard, uninstalling and reinstalling the keyboard without any avail.



Whenever, I switch to Avro keyboard, I get texts in Arabic.










share|improve this question























  • I installed the thing on my 16.10, and I don't get a keyboard layout chart at all... One thing you may want to do is to install the ibus-m17n package and try the Bengali options provided by that package.
    – Gunnar Hjalmarsson
    Apr 12 '17 at 14:16






  • 1




    Same issue. It was working on 16.10 but not working on 17.04
    – Pavak Paul
    Apr 14 '17 at 13:09










  • @GunnarHjalmarsson I installed ibus-m17n, no improvement. Thanks anyway.
    – Masroor
    Apr 15 '17 at 7:27












up vote
6
down vote

favorite
1









up vote
6
down vote

favorite
1






1





I upgraded one of my machines to Ubuntu 17.04. May be it is related, may be it is not, but for this machine, Avro Bengali keyboard switched to Malay (Jawi) after upgrade.



My other two machines, running Ubuntu 16.04 are working fine.



Please see these self explanatory screenshots.



enter image description here



enter image description here



I tried removing and re-adding the keyboard, uninstalling and reinstalling the keyboard without any avail.



Whenever, I switch to Avro keyboard, I get texts in Arabic.










share|improve this question















I upgraded one of my machines to Ubuntu 17.04. May be it is related, may be it is not, but for this machine, Avro Bengali keyboard switched to Malay (Jawi) after upgrade.



My other two machines, running Ubuntu 16.04 are working fine.



Please see these self explanatory screenshots.



enter image description here



enter image description here



I tried removing and re-adding the keyboard, uninstalling and reinstalling the keyboard without any avail.



Whenever, I switch to Avro keyboard, I get texts in Arabic.







keyboard keyboard-layout ibus-avro






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Apr 14 '17 at 16:11

























asked Apr 12 '17 at 13:02









Masroor

1,57631941




1,57631941











  • I installed the thing on my 16.10, and I don't get a keyboard layout chart at all... One thing you may want to do is to install the ibus-m17n package and try the Bengali options provided by that package.
    – Gunnar Hjalmarsson
    Apr 12 '17 at 14:16






  • 1




    Same issue. It was working on 16.10 but not working on 17.04
    – Pavak Paul
    Apr 14 '17 at 13:09










  • @GunnarHjalmarsson I installed ibus-m17n, no improvement. Thanks anyway.
    – Masroor
    Apr 15 '17 at 7:27
















  • I installed the thing on my 16.10, and I don't get a keyboard layout chart at all... One thing you may want to do is to install the ibus-m17n package and try the Bengali options provided by that package.
    – Gunnar Hjalmarsson
    Apr 12 '17 at 14:16






  • 1




    Same issue. It was working on 16.10 but not working on 17.04
    – Pavak Paul
    Apr 14 '17 at 13:09










  • @GunnarHjalmarsson I installed ibus-m17n, no improvement. Thanks anyway.
    – Masroor
    Apr 15 '17 at 7:27















I installed the thing on my 16.10, and I don't get a keyboard layout chart at all... One thing you may want to do is to install the ibus-m17n package and try the Bengali options provided by that package.
– Gunnar Hjalmarsson
Apr 12 '17 at 14:16




I installed the thing on my 16.10, and I don't get a keyboard layout chart at all... One thing you may want to do is to install the ibus-m17n package and try the Bengali options provided by that package.
– Gunnar Hjalmarsson
Apr 12 '17 at 14:16




1




1




Same issue. It was working on 16.10 but not working on 17.04
– Pavak Paul
Apr 14 '17 at 13:09




Same issue. It was working on 16.10 but not working on 17.04
– Pavak Paul
Apr 14 '17 at 13:09












@GunnarHjalmarsson I installed ibus-m17n, no improvement. Thanks anyway.
– Masroor
Apr 15 '17 at 7:27




@GunnarHjalmarsson I installed ibus-m17n, no improvement. Thanks anyway.
– Masroor
Apr 15 '17 at 7:27










2 Answers
2






active

oldest

votes

















up vote
4
down vote



accepted
+50










This seems to happen because of the new XKB symbols file bn which was created as a fix of this bug. As far as I can tell that file is redundant, since the name of the layout - Malay (Jawi) - is already present in the symbols file my. Currently there are two entries named Malay (Jawi) in the list of input sources.



Anyway, removing or renaming the bn symbols file seems to fix this issue.



cd /usr/share/X11/xkb/symbols
sudo mv bn bn.bak


Edit:



I filed this bug, which has been accepted and will affect version 2.21 of xkb-data.



Edit II:



The issue is also about to be fixed in v2 of ibus-avro.




Edit III:



It seems moving the file make wayland session on latest Ubuntu inaccessible. Also the developers of ibus-avro suggested another workaround which fixes the issue without interfering with wayland session. This is documented here



In short, you need to edit the file at /usr/share/ibus/component/ibus-avro.xml



sudo vim /usr/share/ibus/component/ibus-avro.xml


On line 20, change



<layout>bn</layout>


to



<layout>us</layout>


Save the file and restart your session.






share|improve this answer


















  • 1




    That fixed it. Who could of imagined such a reason? Thanks a lot.
    – Masroor
    Apr 17 '17 at 6:17










  • I think I've found a similar bug, mine switches to Arabic instead of Malay. If I move the symbol, then Gnome wayland session breaks. So, I searched and found the fix here on avro's git repo. It fixed the problem nicely!
    – Anwar
    Jul 13 '17 at 6:54






  • 1




    @Anwar: Malay (Jawi) is written using an Arabic script, so it's most likely the same issue. Thanks for letting us know that it's about to be fixed in ibus-avro.
    – Gunnar Hjalmarsson
    Jul 13 '17 at 14:47










  • You may want to include that information into the answer.
    – Anwar
    Jul 13 '17 at 14:51






  • 1




    @Anwar: Please feel free to edit the answer in that direction. You are using the thing, after all. ;) (Hopefully the problem will go away in 18.04 with an update of xkb-data.)
    – Gunnar Hjalmarsson
    Dec 11 '17 at 14:39

















up vote
0
down vote













This does solve the problem: https://github.com/sarim/ibus-avro



You can try out my script which automatically fetches everything and installs avro for you. Just download or clone my repository: https://github.com/pavakpaul/ibus-avro-installer-for-ubuntu and execute install-ibus-avro-for-ubuntu-wily.sh






share|improve this answer



















    protected by Community♦ Oct 24 '17 at 0:52



    Thank you for your interest in this question.
    Because it has attracted low-quality or spam answers that had to be removed, posting an answer now requires 10 reputation on this site (the association bonus does not count).



    Would you like to answer one of these unanswered questions instead?














    2 Answers
    2






    active

    oldest

    votes








    2 Answers
    2






    active

    oldest

    votes









    active

    oldest

    votes






    active

    oldest

    votes








    up vote
    4
    down vote



    accepted
    +50










    This seems to happen because of the new XKB symbols file bn which was created as a fix of this bug. As far as I can tell that file is redundant, since the name of the layout - Malay (Jawi) - is already present in the symbols file my. Currently there are two entries named Malay (Jawi) in the list of input sources.



    Anyway, removing or renaming the bn symbols file seems to fix this issue.



    cd /usr/share/X11/xkb/symbols
    sudo mv bn bn.bak


    Edit:



    I filed this bug, which has been accepted and will affect version 2.21 of xkb-data.



    Edit II:



    The issue is also about to be fixed in v2 of ibus-avro.




    Edit III:



    It seems moving the file make wayland session on latest Ubuntu inaccessible. Also the developers of ibus-avro suggested another workaround which fixes the issue without interfering with wayland session. This is documented here



    In short, you need to edit the file at /usr/share/ibus/component/ibus-avro.xml



    sudo vim /usr/share/ibus/component/ibus-avro.xml


    On line 20, change



    <layout>bn</layout>


    to



    <layout>us</layout>


    Save the file and restart your session.






    share|improve this answer


















    • 1




      That fixed it. Who could of imagined such a reason? Thanks a lot.
      – Masroor
      Apr 17 '17 at 6:17










    • I think I've found a similar bug, mine switches to Arabic instead of Malay. If I move the symbol, then Gnome wayland session breaks. So, I searched and found the fix here on avro's git repo. It fixed the problem nicely!
      – Anwar
      Jul 13 '17 at 6:54






    • 1




      @Anwar: Malay (Jawi) is written using an Arabic script, so it's most likely the same issue. Thanks for letting us know that it's about to be fixed in ibus-avro.
      – Gunnar Hjalmarsson
      Jul 13 '17 at 14:47










    • You may want to include that information into the answer.
      – Anwar
      Jul 13 '17 at 14:51






    • 1




      @Anwar: Please feel free to edit the answer in that direction. You are using the thing, after all. ;) (Hopefully the problem will go away in 18.04 with an update of xkb-data.)
      – Gunnar Hjalmarsson
      Dec 11 '17 at 14:39














    up vote
    4
    down vote



    accepted
    +50










    This seems to happen because of the new XKB symbols file bn which was created as a fix of this bug. As far as I can tell that file is redundant, since the name of the layout - Malay (Jawi) - is already present in the symbols file my. Currently there are two entries named Malay (Jawi) in the list of input sources.



    Anyway, removing or renaming the bn symbols file seems to fix this issue.



    cd /usr/share/X11/xkb/symbols
    sudo mv bn bn.bak


    Edit:



    I filed this bug, which has been accepted and will affect version 2.21 of xkb-data.



    Edit II:



    The issue is also about to be fixed in v2 of ibus-avro.




    Edit III:



    It seems moving the file make wayland session on latest Ubuntu inaccessible. Also the developers of ibus-avro suggested another workaround which fixes the issue without interfering with wayland session. This is documented here



    In short, you need to edit the file at /usr/share/ibus/component/ibus-avro.xml



    sudo vim /usr/share/ibus/component/ibus-avro.xml


    On line 20, change



    <layout>bn</layout>


    to



    <layout>us</layout>


    Save the file and restart your session.






    share|improve this answer


















    • 1




      That fixed it. Who could of imagined such a reason? Thanks a lot.
      – Masroor
      Apr 17 '17 at 6:17










    • I think I've found a similar bug, mine switches to Arabic instead of Malay. If I move the symbol, then Gnome wayland session breaks. So, I searched and found the fix here on avro's git repo. It fixed the problem nicely!
      – Anwar
      Jul 13 '17 at 6:54






    • 1




      @Anwar: Malay (Jawi) is written using an Arabic script, so it's most likely the same issue. Thanks for letting us know that it's about to be fixed in ibus-avro.
      – Gunnar Hjalmarsson
      Jul 13 '17 at 14:47










    • You may want to include that information into the answer.
      – Anwar
      Jul 13 '17 at 14:51






    • 1




      @Anwar: Please feel free to edit the answer in that direction. You are using the thing, after all. ;) (Hopefully the problem will go away in 18.04 with an update of xkb-data.)
      – Gunnar Hjalmarsson
      Dec 11 '17 at 14:39












    up vote
    4
    down vote



    accepted
    +50







    up vote
    4
    down vote



    accepted
    +50




    +50




    This seems to happen because of the new XKB symbols file bn which was created as a fix of this bug. As far as I can tell that file is redundant, since the name of the layout - Malay (Jawi) - is already present in the symbols file my. Currently there are two entries named Malay (Jawi) in the list of input sources.



    Anyway, removing or renaming the bn symbols file seems to fix this issue.



    cd /usr/share/X11/xkb/symbols
    sudo mv bn bn.bak


    Edit:



    I filed this bug, which has been accepted and will affect version 2.21 of xkb-data.



    Edit II:



    The issue is also about to be fixed in v2 of ibus-avro.




    Edit III:



    It seems moving the file make wayland session on latest Ubuntu inaccessible. Also the developers of ibus-avro suggested another workaround which fixes the issue without interfering with wayland session. This is documented here



    In short, you need to edit the file at /usr/share/ibus/component/ibus-avro.xml



    sudo vim /usr/share/ibus/component/ibus-avro.xml


    On line 20, change



    <layout>bn</layout>


    to



    <layout>us</layout>


    Save the file and restart your session.






    share|improve this answer














    This seems to happen because of the new XKB symbols file bn which was created as a fix of this bug. As far as I can tell that file is redundant, since the name of the layout - Malay (Jawi) - is already present in the symbols file my. Currently there are two entries named Malay (Jawi) in the list of input sources.



    Anyway, removing or renaming the bn symbols file seems to fix this issue.



    cd /usr/share/X11/xkb/symbols
    sudo mv bn bn.bak


    Edit:



    I filed this bug, which has been accepted and will affect version 2.21 of xkb-data.



    Edit II:



    The issue is also about to be fixed in v2 of ibus-avro.




    Edit III:



    It seems moving the file make wayland session on latest Ubuntu inaccessible. Also the developers of ibus-avro suggested another workaround which fixes the issue without interfering with wayland session. This is documented here



    In short, you need to edit the file at /usr/share/ibus/component/ibus-avro.xml



    sudo vim /usr/share/ibus/component/ibus-avro.xml


    On line 20, change



    <layout>bn</layout>


    to



    <layout>us</layout>


    Save the file and restart your session.







    share|improve this answer














    share|improve this answer



    share|improve this answer








    edited Dec 11 '17 at 17:03









    Anwar

    54.5k20143248




    54.5k20143248










    answered Apr 15 '17 at 19:13









    Gunnar Hjalmarsson

    17.9k23059




    17.9k23059







    • 1




      That fixed it. Who could of imagined such a reason? Thanks a lot.
      – Masroor
      Apr 17 '17 at 6:17










    • I think I've found a similar bug, mine switches to Arabic instead of Malay. If I move the symbol, then Gnome wayland session breaks. So, I searched and found the fix here on avro's git repo. It fixed the problem nicely!
      – Anwar
      Jul 13 '17 at 6:54






    • 1




      @Anwar: Malay (Jawi) is written using an Arabic script, so it's most likely the same issue. Thanks for letting us know that it's about to be fixed in ibus-avro.
      – Gunnar Hjalmarsson
      Jul 13 '17 at 14:47










    • You may want to include that information into the answer.
      – Anwar
      Jul 13 '17 at 14:51






    • 1




      @Anwar: Please feel free to edit the answer in that direction. You are using the thing, after all. ;) (Hopefully the problem will go away in 18.04 with an update of xkb-data.)
      – Gunnar Hjalmarsson
      Dec 11 '17 at 14:39












    • 1




      That fixed it. Who could of imagined such a reason? Thanks a lot.
      – Masroor
      Apr 17 '17 at 6:17










    • I think I've found a similar bug, mine switches to Arabic instead of Malay. If I move the symbol, then Gnome wayland session breaks. So, I searched and found the fix here on avro's git repo. It fixed the problem nicely!
      – Anwar
      Jul 13 '17 at 6:54






    • 1




      @Anwar: Malay (Jawi) is written using an Arabic script, so it's most likely the same issue. Thanks for letting us know that it's about to be fixed in ibus-avro.
      – Gunnar Hjalmarsson
      Jul 13 '17 at 14:47










    • You may want to include that information into the answer.
      – Anwar
      Jul 13 '17 at 14:51






    • 1




      @Anwar: Please feel free to edit the answer in that direction. You are using the thing, after all. ;) (Hopefully the problem will go away in 18.04 with an update of xkb-data.)
      – Gunnar Hjalmarsson
      Dec 11 '17 at 14:39







    1




    1




    That fixed it. Who could of imagined such a reason? Thanks a lot.
    – Masroor
    Apr 17 '17 at 6:17




    That fixed it. Who could of imagined such a reason? Thanks a lot.
    – Masroor
    Apr 17 '17 at 6:17












    I think I've found a similar bug, mine switches to Arabic instead of Malay. If I move the symbol, then Gnome wayland session breaks. So, I searched and found the fix here on avro's git repo. It fixed the problem nicely!
    – Anwar
    Jul 13 '17 at 6:54




    I think I've found a similar bug, mine switches to Arabic instead of Malay. If I move the symbol, then Gnome wayland session breaks. So, I searched and found the fix here on avro's git repo. It fixed the problem nicely!
    – Anwar
    Jul 13 '17 at 6:54




    1




    1




    @Anwar: Malay (Jawi) is written using an Arabic script, so it's most likely the same issue. Thanks for letting us know that it's about to be fixed in ibus-avro.
    – Gunnar Hjalmarsson
    Jul 13 '17 at 14:47




    @Anwar: Malay (Jawi) is written using an Arabic script, so it's most likely the same issue. Thanks for letting us know that it's about to be fixed in ibus-avro.
    – Gunnar Hjalmarsson
    Jul 13 '17 at 14:47












    You may want to include that information into the answer.
    – Anwar
    Jul 13 '17 at 14:51




    You may want to include that information into the answer.
    – Anwar
    Jul 13 '17 at 14:51




    1




    1




    @Anwar: Please feel free to edit the answer in that direction. You are using the thing, after all. ;) (Hopefully the problem will go away in 18.04 with an update of xkb-data.)
    – Gunnar Hjalmarsson
    Dec 11 '17 at 14:39




    @Anwar: Please feel free to edit the answer in that direction. You are using the thing, after all. ;) (Hopefully the problem will go away in 18.04 with an update of xkb-data.)
    – Gunnar Hjalmarsson
    Dec 11 '17 at 14:39












    up vote
    0
    down vote













    This does solve the problem: https://github.com/sarim/ibus-avro



    You can try out my script which automatically fetches everything and installs avro for you. Just download or clone my repository: https://github.com/pavakpaul/ibus-avro-installer-for-ubuntu and execute install-ibus-avro-for-ubuntu-wily.sh






    share|improve this answer
























      up vote
      0
      down vote













      This does solve the problem: https://github.com/sarim/ibus-avro



      You can try out my script which automatically fetches everything and installs avro for you. Just download or clone my repository: https://github.com/pavakpaul/ibus-avro-installer-for-ubuntu and execute install-ibus-avro-for-ubuntu-wily.sh






      share|improve this answer






















        up vote
        0
        down vote










        up vote
        0
        down vote









        This does solve the problem: https://github.com/sarim/ibus-avro



        You can try out my script which automatically fetches everything and installs avro for you. Just download or clone my repository: https://github.com/pavakpaul/ibus-avro-installer-for-ubuntu and execute install-ibus-avro-for-ubuntu-wily.sh






        share|improve this answer












        This does solve the problem: https://github.com/sarim/ibus-avro



        You can try out my script which automatically fetches everything and installs avro for you. Just download or clone my repository: https://github.com/pavakpaul/ibus-avro-installer-for-ubuntu and execute install-ibus-avro-for-ubuntu-wily.sh







        share|improve this answer












        share|improve this answer



        share|improve this answer










        answered Apr 27 '17 at 9:37









        Pavak Paul

        85711026




        85711026















            protected by Community♦ Oct 24 '17 at 0:52



            Thank you for your interest in this question.
            Because it has attracted low-quality or spam answers that had to be removed, posting an answer now requires 10 reputation on this site (the association bonus does not count).



            Would you like to answer one of these unanswered questions instead?


            Popular posts from this blog

            pylint3 and pip3 broken

            Missing snmpget and snmpwalk

            How to enroll fingerprints to Ubuntu 17.10 with VFS491