Description of problem: When we use ibus-sayura, it always delete the previous character expect the starting character of the sentence. Version-Release number of selected component (if applicable): Fedora 28 x86_64 How reproducible: Steps to Reproduce: 1. Start LibreOffice 6.0 or gedit 2. Switch to Sayura imput method 3. Type keys 'DnisHwk ' (space to start next word but now space also delete the previous key due to this issue) Actual results: ඩඉහ් Expected results: ඩනිෂ්ක This is how I write my own name 'Danishka' in Sinhala. This issue causing major problem to all government and pirate organizations as well as individuals who use Fedora as they can't type Sinhala at all. Additional info: Seems the same issue can be reproducible with wijesekara input method. I will add few users who use Wijesekara input method.
I am experiencing the same problem while using Wijesekara keyboard layout. So this seems to be related to ibus-m17n as well. This happens on emacs, gedit and LibreOffice. Fedora version : 28 Steps to reproduce: 1. Start Gedit 2. Switch to Sinhala (wijesekara keyboard layout) 3. Type keys vksIal kjSka 4. Hit space to separate it from the next word. This adds a space to the last character of the first word, and deletes it when you start typing the second word: Example 1: Expected result ඩනිෂ්ක නවීන් (vksIal kjSka) Actual result ඩිෂ් නීන් (vsIa kSka) Example 2 (single word) Expected result ඩනිෂ්ක (vksIal) Actual result ඩිෂ් ක (vsIa l)
Please provide more information. I understood what to type and can get to type the words. I typed those 2 words but now at where/what position you are using delete key?
HI Parag, Thanks for your prompt reply here. When I use ibus-sayura, I use thse keys DnisHwk. ඩනඉෂවක this is the actual (individual characters I get if I type them with a delay to understand the issue) 01. When I type D I get ඩ 02. then n - I get character න => ඩන appearing in the UI. 03. then i - I get the character ඉ but it delete the previous character 'න' and endedup with ඩඉ I was using LibreOffice 6.0 with ibus-sayura.
Delete key was not used during the entire process.
I am not understanding what is happening at your side but I did test Sayura and Wijesekara input methods and both are working fine for me. e.g. If I type in Libreoffice Writer using Sayura "Dni " continuously I got ඩනි. I have not used Delete key here. I have these packages $ rpm -qa m17n-db m17n-lib ibus-m17n harfbuzz pango libreoffice-writer harfbuzz-1.7.5-3.fc28.x86_64 m17n-lib-1.8.0-1.fc28.x86_64 m17n-db-1.8.0-3.fc28.noarch libreoffice-writer-6.0.6.1-5.fc28.x86_64 ibus-m17n-1.3.4-26.fc28.x86_64 pango-1.42.3-1.fc28.x86_64
Created attachment 1476586 [details] Screen capture of issue with ibus
My system have been upgraded from Fedora 27 to Fedora 28. [danishka@hanthana ~]$ rpm -qa m17n-db m17n-lib ibus-m17n ibus-sayura harfbuzz pango libreoffice-writer harfbuzz-1.7.5-3.fc28.i686 m17n-lib-1.8.0-1.fc28.x86_64 libreoffice-writer-6.0.4.2-2.fc28.x86_64 ibus-m17n-1.3.4-25.fc28.x86_64 ibus-sayura-1.3.2-13.fc28.x86_64 m17n-db-1.8.0-3.fc28.noarch pango-1.42.1-2.fc28.i686 pango-1.42.1-2.fc28.x86_64 harfbuzz-1.7.5-3.fc28.x86_64 I noticed that I was using old version of Pango compared to Parag's system. I did updated pango but no luck. [danishka@hanthana ~]$ rpm -qa m17n-db m17n-lib ibus-m17n ibus-sayura harfbuzz pango libreoffice-writer harfbuzz-1.7.5-3.fc28.i686 m17n-lib-1.8.0-1.fc28.x86_64 libreoffice-writer-6.0.4.2-2.fc28.x86_64 ibus-m17n-1.3.4-25.fc28.x86_64 ibus-sayura-1.3.2-13.fc28.x86_64 pango-1.42.3-1.fc28.x86_64 m17n-db-1.8.0-3.fc28.noarch pango-1.42.3-1.fc28.i686 harfbuzz-1.7.5-3.fc28.x86_64
I was also able to reproduce this issue but after upgrading system and restarting does not reproduce this issue. @Danishka please update your system, restart and try again. I see below packages are still not updated at your end. 1. libreoffice-writer-6.0.6.1-5.fc28.x86_64 -> libreoffice-writer-6.0.4.2-2.fc28.x86_64 2. ibus-m17n-1.3.4-26.fc28.x86_64 -> ibus-m17n-1.3.4-25.fc28.x86_64
Hi Pravin, Thanks for the feedback. I have updated the system and rebooted. Now I can't reproduce this issue but lets wait for others to test. Thanks again!
Great, glad to know. Its working for you now.
Any updates here? I think this is working fine. Will close this bug after 1 week if no further updates added here.