sfos-ja / jolla-kbd-flick-jp

Japanese flick-style keyboard for Sailfish OS
GNU Lesser General Public License v2.1
1 stars 3 forks source link

Installation works but I can't "flick" #19

Open AlarithUhde opened 4 years ago

AlarithUhde commented 4 years ago

Hi!

I got the keyboard working, but flicking doesn't work. So I can type は、ら、さ、が etc., but not e.g. ひ. I have patchmanager and the sfos_ja "Japanese keyboard with Anthy" installed as well. I also tried to additionally install the behold "jolla-anthy-jp" and rebooting, but didn't work. Any suggestions?

I'm using Sailfish OS 3.1.0.11 on an Xperia XA2.

knokmki612 commented 4 years ago

Hi! thank you for your reporting

I got the keyboard working, but flicking doesn't work.

It seems the patch didn't work. Maybe need work to follow the update of SFOS 3.1.0.11 (like this: 16a313775ab4be42fbfb534d26356d19a0f49bc0)

I also tried to additionally install the behold "jolla-anthy-jp"

behold version and sfos-ja version of "jolla-anthy-jp" are the same package name. installing the other version will overwrite the others. I think this operation wouldn't affect this issue.

topiasv commented 4 years ago

It seems like the patch is working for me running with patchmanager 3 on the latest cbeta release so I'm pretty sure it should be working on that release as well. Some differences may exist in our device configurations in which case it can be difficult for us to try and debug it on our own since the patch is running just fine for us. However, I did notice some weird issues with patchmanager 3 that sometimes caused patches to stop working altogether, which might be the cause of your issue. I haven't investigated the issue much further since it seemed to solve itself.

In case you're still having issues, we'd like to you to help us find out the issue in our code or report this issue back to the developers of patchmanager 3 in the case it happens to be this issue. To help us find the issue, you can try out these following steps:

  1. Make sure maliit-server has been restarted by running systemctl --user restart maliit-server on the terminal. Rebooting and restarting lipstick should work too.

    If this resolved your problem then the problem was likely because maliit-server was not restarted after the patch (which is unlikely in your case since you restarted the device). If not, move on to step 2

  2. From the settings under patchmanager option whether Japanese Flick Keyboard Support is on. a) If the patch was already on but flicking still doesn't work, make sure maliit-server has been restarted with the command in step 1.

    If the problem is resolved, the problem is likely because maliit-server was not restarted after the patch (unlikely in your case but never hurts to try) If the problem persists the problem is likely in patchmanager 3 and you may move onto step 4

    b) If the patch was not on, then enable the patch and restart maliit-server with the command in step 1 and see if the problem persists.

    If the problem is resolved the likely cause was the patch not being enabled. If the patch is now on and maliit-server has been restarted and flicking still doesn't work, the problem is likely in patchmanager 3 and you may move onto step 3.

    If the patch gives out an error, there is a problem with the patch and we need your help to fix it. Please do the following

    Try installing the patch from the terminal in order to get the error message to help us debug the issue by running the following command: patch -p 1 -d / -i /usr/share/patchmanager/patches/jolla-kbd-flick-jp/unified_diff.patch

    We may also need you to provide some files in case the patchmanager doesn't tell us directly where the issue is. You can find these in the following directories: /usr/share/maliit/plugins/com/jolla/KeyboardBase.qml /usr/share/jolla-settings/pages/text_input/textinput.qml

    With this information we should be able to fix the bug in no time!

  3. If flicking still doesn't work there may be an issue with patchmanager 3. Try installing another (working) patch such as bigger spacebar patch from openrepos and restart lipstick and see if that patch works.

    If the patch is on but doesn't work, the problem is likely in the patchmanager 3 itself and you should move onto step 4. If the patch is on and works, the problem is likely due to some incompatibility issue with our patch and patchmanager 3 which means we got some work to do. You should try step 4 and see if it fixes the issue for you.

  4. The patchmanager 3 itself is either having problems or our patch is somehow incompatible with it. To verify that this is the case, you should try downgrading patchmanager 3 to the last patchmanager 2 version. You may download it from here. After installing the older patchmanager 2 version, try applying the patch again following the instructions in step 2.

    If the flicking still doesn't work, there is something terribly wrong and we will be frantically scratching our heads behind our screens and wonder what the heck is going on. In this case we hope you could help us provide more information about your system and see if we can find the cause of the issue.

I hope this helps you resolve your issue but if it doesn't just report back your findings to us and we can see how we can help you from there.

rrijken1973 commented 4 years ago

have the same problem. enabled under keyboards and it shows up but can only do a, ka, sa, ta etc. flick does not work. enabling in patchmanager 3 gives error. typing above in terminal gives error: cant create temporary file usr/share/jolla-settings/pages/text_input/textinput.qml.o4o8K2Z : permission denied