Hello, after updating to Krita 5.3.1 i’ve found the following crash:
This crash doesn’t happen on 5.3.0.
Device: Huawei Matepad 12x 2024
OS: HarmonyOS 4.2.0
There were a bunch of fixes to text handling in 5.3.1, so that is likely the cause. I can’t make this problem happen on any of my devices though.
Which keyboard application are you using? In the Android settings it should be under Settings → General management → Keyboard list and default, although your device may hide the setting elsewhere.
And does changing the keyboard application to something else get rid of the crash? If you don’t have a different keyboard application, Unexpected Keyboard is a good pick for a keyboard that generally causes few problems.
And what language is your device set to and do you have any special input methods or accessibility options enabled?
I’ve tested it with the preinstalled keyboards on my device (Microsoft Swiftkey and Huawei’s Celia keyboard). Changing the keyboard doesn’t prevent the crash. Following your suggestion i installed Unexpected Keyboard but with the same result.
My initial test was with the system language set to Spanish but changing it in English doesn’t prevent the crash either.
No accessibility options enabled, but i was using the tablet with a physical keyboard attached. Removing the physical keyboard made no change, same crash.
Then unfortunately I have no way of reproducing the problem. Is this the Google Play version of Krita? That might give us a report of the crash.
Krita on Google Play is still on 5.3.0, so no crash yet installing it from there. I have Krita 5.3.1 installed from the apk.
When the Google Play version updates i can try triggering the crash again to see if the report comes through, as Huawei devices get no native Google Play Store and have to use Aurora Store, an open source implementation.
I kind of doubt that it’s going to work then, since the native store is what provides the logs. You’ll probably have to get a log yourself instead. How this works totally depends on the device though, some have a bug reporting system where you can record stuff built in I think, some may be able to use the developer mode, for others you’ll have to use adb from a computer. Either way, I would need a stack trace to tell where the crash is happening to really do anything about it.
I managed to get an adb log of the crash, i hope it is of any help.
Here is just the exception because the forum detects web links and doesn’t let me send the reply. If you need the full log from starting Krita to the exception i can try to upload a txt to some file sharing host:
--------- beginning of crash
04-03 20:16:33.494 13529 13529 E AndroidRuntime: FATAL EXCEPTION: main
04-03 20:16:33.494 13529 13529 E AndroidRuntime: Process: org.krita, PID: 13529
04-03 20:16:33.494 13529 13529 E AndroidRuntime: java.lang.NoSuchMethodError: No virtual method invalidateInput(Landroid/view/View;)V in class Landroid/view/inputmethod/InputMethodManager; or its super classes (declaration of ‘android.view.inputmethod.InputMethodManager’ appears in /system/framework/framework.jar!classes3.dex)
04-03 20:16:33.494 13529 13529 E AndroidRuntime: at org.qtproject.qt5.android.QtActivityDelegate$$ExternalSyntheticApiModelOutline0.m(r8-map-id-de68625f794a6cb9b53c29a96a04e6fb0261fa39ca10aef2ca0e6306d97babf2:1)
04-03 20:16:33.494 13529 13529 E AndroidRuntime: at org.qtproject.qt5.android.QtActivityDelegate.removeEditTextView(r8-map-id-de68625f794a6cb9b53c29a96a04e6fb0261fa39ca10aef2ca0e6306d97babf2:11)
04-03 20:16:33.494 13529 13529 E AndroidRuntime: at org.qtproject.qt5.android.QtActivityDelegate.hideSoftwareKeyboard(r8-map-id-de68625f794a6cb9b53c29a96a04e6fb0261fa39ca10aef2ca0e6306d97babf2:32)
04-03 20:16:33.494 13529 13529 E AndroidRuntime: at org.qtproject.qt5.android.QtNative$13.run(r8-map-id-de68625f794a6cb9b53c29a96a04e6fb0261fa39ca10aef2ca0e6306d97babf2:11)
04-03 20:16:33.494 13529 13529 E AndroidRuntime: at android.os.Handler.handleCallback(Handler.java:966)
04-03 20:16:33.494 13529 13529 E AndroidRuntime: at android.os.Handler.dispatchMessage(Handler.java:110)
04-03 20:16:33.494 13529 13529 E AndroidRuntime: at android.os.Looper.loopOnce(Looper.java:205)
04-03 20:16:33.494 13529 13529 E AndroidRuntime: at android.os.Looper.loop(Looper.java:293)
04-03 20:16:33.494 13529 13529 E AndroidRuntime: at android.app.ActivityThread.loopProcess(ActivityThread.java:10140)
04-03 20:16:33.494 13529 13529 E AndroidRuntime: at android.app.ActivityThread.main(ActivityThread.java:10129)
04-03 20:16:33.494 13529 13529 E AndroidRuntime: at java.lang.reflect.Method.invoke(Native Method)
04-03 20:16:33.494 13529 13529 E AndroidRuntime: at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:593)
04-03 20:16:33.494 13529 13529 E AndroidRuntime: at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1245)
04-03 20:16:33.501 13529 19590 I LifecycleTransaction: activityCallbacks TopResumedActivityChangeItem{onTop=false}
04-03 20:16:33.518 13529 19590 I LifecycleTransaction: lifecycleStateRequest PauseActivityItem{finished=true,userLeaving=false,configChanges=0,dontReport=false}
04-03 20:16:33.535 13529 13529 I Process : Sending signal. PID: 13529 SIG: 9
Thanks, that helps! I have a fix ready here https://invent.kde.org/szaman/qtbase/-/merge_requests/15