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:
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
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
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
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
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.
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
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://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