The release candidate is here for Krita 5.2, this means that we are confident that all the major bugs brought on by the changes in Krita 5.2 have now been fixed, and would like you to give it another round of testing.
Published 15th September, 2023 on krita.org
Please pay extra attention to the following features of Krita, since they got updated or reworked since Beta2:
Here is the full list of bugs (and other minor changes) have been fixed since the second beta:
If youâre using the portable zip files, just open the zip file in Explorer and drag the folder somewhere convenient, then double-click on the Krita icon in the folder. This will not impact an installed version of Krita, though it will share your settings and custom resources with your regular installed version of Krita. For reporting crashes, also get the debug symbols folder.
Note that we are not making 32 bits Windows builds anymore.
The separate gmic-qt AppImage is no longer needed.
(If, for some reason, Firefox thinks it needs to load this as text: to download, right-click on the link.)
Note: if you use macOS Sierra or High Sierra, please check this video to learn how to enable starting developer-signed binaries, instead of just Apple Store binaries.
We consider Krita on ChromeOS as ready for production. Krita on Android is still beta. Krita is not available for Android phones, only for tablets, because the user interface requires a large screen. RC1 packages for Android are signed as usual.
For all downloads, visit https://download.kde.org/unstable/krita/5.2.0-rc1/ and click on Details to get the hashes.
The Linux AppImage and the source .tar.gz and .tar.xz tarballs are signed. This particular release is signed with a non-standard key, you can retrieve is here or download from the public server:
gpg --recv-keys E9FB29E74ADEACC5E3035B8AB69EB4CF7468332F
The signatures are here (filenames ending in .sig).
For people with android crash, try creating new user in your device and install krita. Hasnât crashed yet for me. This is being discussed in bug report site. I will credit the guy who got the workaround. Needto check again.
That is one tough bug to fix. But I am glad there is some workaround. Hopefully it will get fixed soon.
Thanks for testing, I moved your post here in this thread.
I can confirm and I have too encountered this in the nightly build today. Please make a bug report on bugs.kde.org 
What happened to the Tool options docker?
Super awesome! All yâall that have been working tirelessly on this, you are my heroes! Iâm already loving all the fixes.
Now, that being said, I still donât see the ffmpeg baked in that Iâve been so excited about. Iâm working exclusively in Android 13 on a Galaxy Tab S9 Ultra.
For me it is built in when using app image on Linux. I even rendered some test videos and found that MP4 has a limit of 4k with help of @freyalupen
There must be something going on here which needs investigation. Can you somehow clear your earlier settings and start fresh
The mac app bundle requires macOS 11.0 to run, but not mentioned in the blog post.
EDIT: Looks like itâs ARM only binary.
Same, i tried the nightly too and both says ffmpeg not found. Looks like android doesnât have that facility like in desktop version
FFmpegâs absence on Android seems like a packaging issue, that the ffmpeg binary isnât copied into the .apk.
thanks for testing! it appears we messed up something with the build process
So a quick question:
In the former builds I was unable to properly export animations through FFmpeg.
Is that possible in this release candidate or do I have to wait for the final version?
I was able to export a timelapse using built in ffmpeg. The mp4 is limited to 4k size which is a limit imposed by the opencodec and not us. So a size smaller than 4k us good I guess. Other than that it worked okay. Some users reported that it is not working on android due to possible packaging issue, I would like to call others to test this under windows and macos too so that in final release all this is sorted out. This is a major change so it will have some issues when starting out just help us getting it ironed out by testing in various scenarios
Is it possible that this Mac version is Apple Silicon only?
Iâve got the latest MacOS Ventura on an Intel MacMini and the OS says that I canât run Krita on this OS.
Also icon shows up like this:
Yes as @IvanYossi said the packaging got messed up it should be a universal build. Wait for some time may be new files will be uploaded.
No problem! I will! Thanks for letting me know!
Thanks @raghukamath ! I wouldnât even consider trying to export at 4k, so I think I can safely install
Hmmm, the new start screen makes opening up a comic manager project a bit more cumbersome. Before, I could see the comics manager docker on the start screen, so I could go directly to the âOpen projectâ button of the comics manager, and then I would open all my images from the comic manager docker.
Now, to see the comic manager, I have to open an image first. Even more annoying since the pages I open with the comics manager donât show up among the most recently opened images (not a new thing, they never did) so Iâm basically opening a random file I donât need need just to see the comics manager, plus while working I have to be careful to always keep at least one image open lest I go back to the dockerless start screen.
Shouldnât it be possible to display at least some dockers on the start screen? I donât think the comics manager is the only docker out there that does some file manager-y stuff that people want to be able to access without having an image open.
