[krita] [Bug 472705] 5.2 Android: App crashes randomly for unknown reasons, except when running app on a second user account
https://bugs.kde.org/show_bug.cgi?id=472705 --- Comment #62 from AppTest --- I just did some testing, and I can confirm this is an accessibility app issue. I know this because I was able to reproduce the crashing on the second user account too! Here are the steps I took to reproduce the crash: Samsung Galaxy Tab S8 Plus Android 13 with October 2023 security patch Samsung One UI 5.1.1 Krita 5.2.1 arm64 apk ( https://download.kde.org/stable/krita/5.2.1/krita-arm64-v8a-5.2.1-release-signed.apk ) Accessibility app that causes crashing: Google Voice Access ( https://play.google.com/store/apps/details?id=com.google.android.apps.accessibility.voiceaccess ) 1. Go to Settings -> Accessibility -> Installed Apps -> Voice Access, and turn the switch from Off to On. Be sure to setup voice access if you haven't done so (it has to download a voice file during setup), and make sure notifications for it are on. Once it's done, you'll have a notification called "Voice Access: Tap to start". Tap it, and you'll get a blue bubble with "." on the corner to confirm it is active. 2. Do a fresh install of Krita 5.2.1, and launch it. 3. Start a new drawing with a 5000x4000 resolution. Then, on the Advanced Color Selector docker, change the brush color to anything else. 4. Krita will crash. If it doesn't, repeat step 3 until it does, without closing any open documents. (It should definitely crash after repeating step 3 two to three more times.) 5. Notice that this happens with Voice Access enabled. Now, go back to the device's setting app and turn Voice Access off (the notification should disappear). 6. This time launch Krira again, and repeat step 3 several times, without closing any open documents. You will see that it stopped crashing! -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 472705] 5.2 Android: App crashes randomly for unknown reasons, except when running app on a second user account
https://bugs.kde.org/show_bug.cgi?id=472705 --- Comment #61 from AppTest --- Interesting find! If this is true, it would explain why I wasn't getting crashes on the secondary user: because I went straight to installing Krita without enabling accessibility apps. I too am a user of accessibility apps daily, I got Magnification, Google Accessibility Suite, and Google Voice Access enabled. I haven't tested what turning these off does yet, but it seems the above comments are sure. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 472705] 5.2 Android: App crashes randomly for unknown reasons, except when running app on a second user account
https://bugs.kde.org/show_bug.cgi?id=472705 --- Comment #60 from abh...@gmail.com --- This is to confirm that accessibility indeed is the root cause. I have enabled a special bubble to control volume digitally on samsung and that was causing the crash. Tested on both nightly and 5.2. Many thanks to @edward @shazam, kindly look into this. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 472705] 5.2 Android: App crashes randomly for unknown reasons, except when running app on a second user account
https://bugs.kde.org/show_bug.cgi?id=472705 --- Comment #59 from abh...@gmail.com --- (In reply to Edward Mowah from comment #58) > ENABLING ACCESSIBILITY APPLICATIONS (SUCH AS BITWARDEN AND MICROSOFT > AUTHENTICATOR) IS CAUSING KRITA TO CRASH > > I backed up my device files, apps and settings and did a factory reset > (Galaxy Tab S9 Ultra) > After reset, I didn't connect to any network at the beginning. > I also didn't logon to any account (Google / Samsung) > No application updates, no setting changed besides switching device to dark > mode. > I uninstalled / disabled 3rd party apps / bloat like always. > > Krita ran without crashing. > > As soon as I restored everything from my back up including apps and device > settings, krita began crashing again. > > I repeated the process but this time I logged in to Google and Samsung right > from the beginning after reset and even updated applications. > I uninstalled bloat like always. > But I didn't install any other application or change any settings (besides > switching to dark mode) > > Krita runs fine. > > From here for each app installed and for each settings changed, I will > opened Krita and see if it will crash. > > Krita ran without crashing until I installed and set up Bitwarden on my > device. > > At first I thought it was just Bitwarden itself, because Krita ran fine up > until I set Bitwarden up, but then Microsoft Authenticator also Caused Krita > to crash. > Both apps have similar settings and one among them is enabling them in > Accessibility Settings. > > I found that when either app was enabled under Accessibility settings, krita > crashed. > By disabling them in Accessibility settings I am able to run krita without a > crash. > > Can someone else who's having this issue confirm that they have any app > enabled under accessibility settings? (Maybe it's not just Bitwarden and > Microsoft Authenticator) Nice Find Edward, I will check the same once I reach back home and this could potentially explain why the second user is working for me as i don't have any app there with accessibility access. Ok while posting this I tested this on my mi11t pro which has never crashed ever, and right after giving accessibility access, right on the money krita crashed. I can confirm that this finding is correct. Giving access to accessibility crashes Krita as per my method (add layers, group them, and select one layer) Brawo Edward. I will also try to take Logcat on mobile since I don't have a pc access. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 472705] 5.2 Android: App crashes randomly for unknown reasons, except when running app on a second user account
https://bugs.kde.org/show_bug.cgi?id=472705 --- Comment #58 from Edward Mowah --- ENABLING ACCESSIBILITY APPLICATIONS (SUCH AS BITWARDEN AND MICROSOFT AUTHENTICATOR) IS CAUSING KRITA TO CRASH I backed up my device files, apps and settings and did a factory reset (Galaxy Tab S9 Ultra) After reset, I didn't connect to any network at the beginning. I also didn't logon to any account (Google / Samsung) No application updates, no setting changed besides switching device to dark mode. I uninstalled / disabled 3rd party apps / bloat like always. Krita ran without crashing. As soon as I restored everything from my back up including apps and device settings, krita began crashing again. I repeated the process but this time I logged in to Google and Samsung right from the beginning after reset and even updated applications. I uninstalled bloat like always. But I didn't install any other application or change any settings (besides switching to dark mode) Krita runs fine. >From here for each app installed and for each settings changed, I will opened Krita and see if it will crash. Krita ran without crashing until I installed and set up Bitwarden on my device. At first I thought it was just Bitwarden itself, because Krita ran fine up until I set Bitwarden up, but then Microsoft Authenticator also Caused Krita to crash. Both apps have similar settings and one among them is enabling them in Accessibility Settings. I found that when either app was enabled under Accessibility settings, krita crashed. By disabling them in Accessibility settings I am able to run krita without a crash. Can someone else who's having this issue confirm that they have any app enabled under accessibility settings? (Maybe it's not just Bitwarden and Microsoft Authenticator) -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 472705] 5.2 Android: App crashes randomly for unknown reasons, except when running app on a second user account
https://bugs.kde.org/show_bug.cgi?id=472705 --- Comment #57 from AppTest --- Didn't realize the link had adb instructions. Sorry, my mistake. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 472705] 5.2 Android: App crashes randomly for unknown reasons, except when running app on a second user account
https://bugs.kde.org/show_bug.cgi?id=472705 --- Comment #56 from AppTest --- (In reply to sh_zam from comment #55) > It seems like this could be happening due to something on Java side and a > way to figure out might to share a logcat of app, but it requires > installing adb. If that's not possible something like > https://developer.android.com/studio/debug/bug-report might be really > helpful. But due to sometimes sensitive nature of the bug-report file I’d > recommend you to email it to me on: shzam [at] sdf.org Do you have instructions on how to do the first suggestion? The adb process, for those of us with less tech knowledge. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 472705] 5.2 Android: App crashes randomly for unknown reasons, except when running app on a second user account
https://bugs.kde.org/show_bug.cgi?id=472705 --- Comment #55 from sh_zam --- It seems like this could be happening due to something on Java side and a way to figure out might to share a logcat of app, but it requires installing adb. If that's not possible something like https://developer.android.com/studio/debug/bug-report might be really helpful. But due to sometimes sensitive nature of the bug-report file I’d recommend you to email it to me on: shzam [at] sdf.org -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 472705] 5.2 Android: App crashes randomly for unknown reasons, except when running app on a second user account
https://bugs.kde.org/show_bug.cgi?id=472705 AppTest changed: What|Removed |Added Summary|5.2 Android: App crashes|5.2 Android: App crashes |shortly after transforming |randomly for unknown |multiple layers or at |reasons, except when |random moments |running app on a second ||user account -- You are receiving this mail because: You are watching all bug changes.
