Those errors are caused by Krita’s update of Qt. They must be solved by the plugin developers. (But it’s an easy fix, the float variables just need to be wrapped in int().)
1 Like
The creator of Pigment.O @EyeOdin stated on this post to uninstall the plugin before updating to Krita 5.2 as the new python version breaks the plugin and there hasen’t been a bug fix for it yet. The creator also stated all bug reports pertaining to that will be ignored.
I think probably once 5.2 will be released and stabilised the plugin authors will start to release plugins for it.
@gravitationalflyp If your comment is about 5.3, we should move your post into its own topic as this one is for feedback on the 5.2 second beta.
I believe you are getting this error because the apk has not been signed for this beta update.
Sorry but krita 5.2 nuked me out of existence. All my plugins were affected and effectively removed in some way or another.
Yes the float issue is fixable and I fixed it in 1 day but there a issue particular to only me almost I guess. I was rewriting all my plugins to release all at the same time when this changed showed up.
I was forced to release the ones on hold just so they can exist and even so they do not run. And those that would run with the no dockers boot are currently too incomplete because they are being fixed of all other bugs. I am not gonna make a third bug fix version of the project, 2 versions for each project is more than enough.
So now things will have to wait.
Also I dislike 5.2 heavily and I will not be using it. Regardless if I want to give support to older versions or regressions because it will happen eventually. I need to code in the older version because if I make a mistake it will pop up instantly unlike 5.2 that stops everything from running by the looks of it until the document is open case happens.
The int problem is the least of my issues despite being an exquisite nuisance like I have never seen before in python. Because it wants to change things that only work as float and I have juggle its representation to int despite doing it automatically in the previous version of Qt.
Any workaround for this? I’m not familiar with how signed or unsigned apks work unfortunately 
I think for now there is no way. but future release or nightly might have signed apk. I do not know how to run unsigned apk.
1 Like
OK I will wait 
I reported a bug for 5.1.5 and am hoping it’s been fixed on 5.2. Fingers crossed! Have a great day.
Do you have access to a desktop, you can test it there.
KanvasBuddy has been patched. Just re-download the plugin and it should work with Krita 5.2.
Is there going to be a third beta or do you think beta 2 is the last one before RC1?
1 Like
Yes there is, but it requires a computer to side load the app and is a bit complicated to get started. I’m just waiting for the next signed apk download myself. 
Hello, I installed the latest version of Krita (5.2.0 beta 2) and noticed that whenever I try to “call” the pop-up palette, it either doesn’t show or it does randomly. I tried to change the shortcut in my tablet (Huion Kamvas 16 Pro) to see if by any chance the pen was giving me problems, but nothing changed. Surprisingly enough, when I use the right click on my mouse, it works just fine.
Once I noticed such detail, I decided to see if the tablet was the problem by using the right click shortcut on the pen in other apps (Medibang Paint, Paint Tool Sai, etc) but the pen works just fine in all of them except for Krita.
I believe this is some kind of bug? Thanks in advance!
Thank you for testing, @Queuedpotato. Your post has been moved into the thread where 5.2 Beta testing results are captured.
1 Like
@Queuedpotato Which operating system and version are you using?
A right-click signal from a mouse is no different from a right-click signal from a tablet.
That suggests a problem on the tablet side.
Have you used any other previous version of krita and if so, was everything ok there?
Your Huion tablet should have the facility to create separate profiles for different applications. If you’ve created a profile for krita, delete it, close the Huion config app then restart your PC then remake a profile for krita.
Hello! I’m using Windows 11 (22H2)
Until this version of Krita, everything worked just fine. This version is the only one giving me this issue.
Anyway, I’ll redo the profile for Krita and see if it works. Thank you for the suggestion!
1 Like
Hello, not sure if anyone encountered this yet, but it seems I found a new hang (near endless loop?). Reproduced in 5.2 (5d1d1a1c2b0b052a89c8f3bc6785893130e798ae) Windows 11:
- Launch Krita
- Create a New Image
- Open Settings > Dockers > Log Viewer
- In Log Viewer, toggle the first button “Enable Logging”
- Open a new window: Window > New Window
- Try to click inside the new window – Krita will become unresponsive
Looks like all threads get stuck waiting on OS sync primitives, while one of them processes UI events related to the Log Viewer docker. Hopefully someone can make sense out of it 
2 Likes
I can confirm:
- Open Krita.
- Have Log Docker’s logging enabled.
- Open a new window.
- In either window, do something to trigger a log message (open preferences, use a filter, etc).
- Krita hangs.
This seems to be a regression of commit 17ab9bae. It should be reported as a bug.
3 Likes
Do you want me to log it in the bug tracker?