Welcome to the forum, @Flexyflex.
I’ve moved your post into the thread where others have reported the “fatal error” issue on Chromebooks. There are potential workarounds here (such as loading 5.1.5 as that was the last version offered on the Play Store prior to the 5.2.2 update).
Okay, I ran it with adb and can confirm the same error happens in logcat on an x86 chromebook
As for they apk, yes it works. Though note to sideload an apk in chromebooks, you either have to enable developer mode(which requires you to wipe your chromebook) or to install and launch it from adb shell from crostini
I don’t think it is practical to ask people to run it from adb shell and best solution is just running the linux version from crostini directly. You get more features that way anyways
But otherwise, someone has to fix the packaging issue in the play store
So I am guessing Krita wont fix a problem or will take a qhile to fix the problem of Krita not working on a play store version of Krita on Chromebook OS?
Forgive my ignorance, then. I didn’t know if there was anything more complicated required than just installing it side-by-side or uninstalling the Release version to install the Plus version.
If the Nightly build works, then most likely it will be fixed in the next Release build as well, unless there’s a build-type-specific packaging issue happening. The team is aiming to make a 5.2.3 release soon, once the new build system is completely set up, so that question will be answered then.
You install the Linux VM by going into settings/advanced/developers and following the instructions, choosing how much space you want to use. If there is an update available, your chromebook should inform you after the install.
If I install the 5.2.2 apk x86, that works fine too. The issue isn’t in the apk likely but in either the appbundle or in the multi-apk configuration. Or someone uploaded the arm version maybe for the x86 or something. So the it working on 5.2.3 doesn’t matter, what matters is that it is properly in Google Play and same mistake is not made twice
? Were you responding to someone else? Developer mode and Crostini are 2 different things. Though both let you sideload apks but through different means
My point was you don’t have to wipe Chromebook if you get Linux this way any more than you would if you get it another way. I quoted you so I made no mistake.
Sometimes we can highlight things and not realize we are quoting so it can happen
That said, I never said that you do. Read my entire paragraph:
“As for they apk, yes it works. Though note to sideload an apk in chromebooks, you either have to enable developer mode(which requires you to wipe your chromebook) or to install and launch it from adb shell from crostini”
Developer mode lets you load up apks directly without needing linux, but requires a wipe. The other way is through adb and linux.
Is there a way to download Krita on linux that will still let you have pen pressure? This Google Play issue really has been bothering me, and there seems to be no fix right now.
Krita on linux has pen pressure, but not on chromebooks because linux is ran in a VM. And google doesn’t allow usb passthrough so any pen input counts as a touchpad/mouse
It may be possible with things like Crouton or if you load up linux directly on the chromebook, but otherwise until google adds usb passthrough it is not possible
Your only option in that case is to load up the linux vm, download adb and use adb to install the apk directly if you have the issue above. Or wait until it gets fixed in the store
Hey, we’re currently trying to solve this. We’ve just created an aab package with the new system: https://invent.kde.org/graphics/krita/-/jobs/1767161/artifacts/raw/_packaging/krita-5.2.2-release.aab , this does however require a chromebook in developer mode.
Please check if it works.
I am gonna have to backup the chromebook to wipe it for developer mode, but I was able to install the aab via bundletool if that is good enough. And after I ran it, same issue…
This should be fixed for the next release, now. The test .aab that should work is here: https://invent.kde.org/graphics/krita/-/jobs/1773497/artifacts/file/_packaging/krita-5.2.0-prealpha-release.aab
Been using Krita on my Chromebook for almost three years now rather flawlessly. Downloaded it from the Google Play Store. But as of a week or two ago I haven’t been able to access the app due to a “Fatal Error”. Are there any fixes to this? I rather not have to change anything because how Krita worked before for me was the best for my lifestyle. Any help would be appreciated, made an account here just for this question.
https://krita-artists.org/t/krita-5-2-2-update-fatal-error-on-chromebook/89008
Welcome to the forum.
Hello @Spoona_Benson and welcome to the forum!
This is a known issue and the fix seems to be found. I can not tell how long it will take Google to roll out the fixed version when it gets available on Krita’s homepage, but you could install it manually from there when it gets published.
@AhabGreybeard, @raghukamath, @Sooz: Can you please merge this topic with the mega-topic about this issue?
Michelist
Thank you for the update! I’m happy to hear there’s a fix so all that’s needed is patience now. That makes the uncertainty far easier to bare. Thank you once again for the info.
I installed it through bundletools and can confirm that it worked
yes there is a crash log and this bug happens on krita 5.2.2
Hey, a bit of an update on this: We’ve just submitted a new android package (5.2.2.1) to the play store that has the aab file fixed (as far as I understood the conversation, the way 5.2.2 specifically was packaged was slightly incorrect, confusing the operating system). We now have to wait for google to accept it, and then you should be able to get it as an update.
We will also have another update later (in the coming few weeks that is), as we’re still trying to figure out how to get audio to work on android, as that’s currently not working because there’s something odd going on with the packaging still. We hope to have that fixed soon.