Krita 5.2 Release Candidate is out! Please help us in another round of testing!

I can no longer move the toolbar afterwards, the handle is gone… what should I do?

You only have to open the dialog to configure the toolbars via ‘‘Settings’’ >> ‘‘Configure Toolbars…’’, and you can close this dialog directly without making any changes to get the handles displayed after closing the dialog. Now you can move your toolbars.

Michelist

That’s how I did it, read it up.
Unfortunately these handles are not available, I have to do this again every time I start, so I can see them working.

I have reported this bug here - 474859 – ffmpeg is missing from release candidate android build and it is marked as a release blocker.
Edit: I spoke too soon, there is a limitation in android which is hindering ffmpeg, but the devs are working on it, it might take some more time.

here is the work that is being done to address this - Commits · ffmpeg-on-android · Sharaf Zaman / Krita · GitLab

3 Likes

Hello! I wanted to report that Krita 5.2-rc1 (git 6adf588) on Mac seems to have an issue with animation rendering. After the animation is rendered, the frame0001.png file is not deleted while all the other frames are correctly deleted. The next iteration of the rendering will then be wrong by using that pre-existing file. This was not a problem on 5.1

5 Likes

I just want to remind the devs there is a possibility of segfault any time you press ctrl + z in krita. Bug report is here:
https://bugs.kde.org/show_bug.cgi?id=474835
This happens in GNU/Linux and has also happened in windows. Both 5.1.5 stable and 5.2 RC1.
This really should be looked into before releasing RC2 or stable.

2 Likes

I realize this is still a work in progress but I’ve noticed the program feels a lot sturdier. I haven’t experienced a single crash or freeze up. A little more milage will help with the confidence, but so far so good. Keep up the good work and thanks!

kritaver

1 Like

Your screenshot shows the Nightly-Branch, that is what is called Krita Next and labeled as “Pipeline Krita_Nightly_Windows_Build” on Jenkins. So, you are an edition too far out (you are testing too fast :wink: ), here it is about the RC-Branch, or “Pipeline Krita_Stable_Windows_Build” on Jenkins, you get there via the link. Today’s build is “5.2.0-rc1-98accb8cc9”.

Michelist

1 Like

Ahh lol thanks for clarifying Michelist! The thing is, this “Krita Next” build that I’m using has the same problem as the current official 5.2 RC-1 release: missing Tool options docker.

If my Jenkins 5.3.0 prealpha build has the same problem as the current 5.2 RC-1 then Jenkins is working with damaged goods. lol

I’ll install the correct RC1 build and see what happens

2 Likes

My bug report has been made a release blocker. I don’t know if this will delay the release even further, only time will be the judge.

Can’t you enable the tool option docker via Settings > Docker > Tool options or is this something else? SOrry if I missed you earlier post in this thread.

May I request you to report this on bugs.kde.org as a regression? Please also post the link to the bug here so that we can subscribe to it.

Sorry I have been told by @dkazakov that he has fixed this already here - Fix removal of duplicated frames in "Only Unique Frames" mode (0ed384a5) · Commits · Graphics / Krita · GitLab

Awesome thanks Raghukamath! Just to confirm the Tools Options docker is completely missing from the Dockers list. Not sure what that duplicated frames problem is referring to but if it involves the Tool Options docker then we’re golden.

@larrycross Look in Configure Krita > General > Tools to see if Tool Options will appear as a docker or in the Toolbar.

(PS - I noticed you wrote to @raghukamath in your last topic but you forgot to add the @ in front of his name. Without that symbol, he will not get pinged with your reply.)

1 Like

Wow , I did not encounter this issue this seems serious. Can you try backing up your krita settings and resetting it to see if it comes back?

On Linux Mint, I’m getting some kind of “is in recursion” error. It pops up a lot of error message boxes when it happens, with the options to either abort or ignore the error - the latter works if I click through them all.

This time Krita crashed so I didn’t get the chance to take a screenshot of the error, but the console had this:

SAFE ASSERT (krita): “!notifier.isInRecursion()” in file /home/appimage/persistent/krita/libs/ui/input/kis_shortcut_matcher.cpp, line 301
Aborted (core dumped)

This seems to only happen when I have not disabled touch on my Cintiq, and put pen to screen right after alt-tabbing back from some other program. It has never happened if I have remembered to disable touch input.

So I forgot to turn touch off again :

BTW with the beta of 5.2 it did not crash, but just spammed the screen full of these errors. Now with the RC, it seems to crash instead.

Edit: I think this happened when I took the cursor to the Krita window, having had the focus in some other program first, then immediately started panning the canvas. Some kind of interaction with a simultaneous touch event maybe.

AHH! that was it thanks @sooz!!! (and thx for the @ tip)

The Tool Options docker was working fine in both the Beta releases. I didn’t notice it missing until RC-1. Was that some new feature added to RC-1 or it’s always been there and I just ignored it? lol

1 Like


One other thing I’ve noticed since the first beta - when I open a project I get this postage stamp sized window. It’s just a momentary thing , then it zooms to full normal size. Is that by design or just some messy programming?

1 Like

I’ve noticed this issue, with the document briefly showing as a small subwindow before turning into a tab, as well. From my investigation it seemed to be a regression appearing between May 18 build (cdb36cb4f0) and May 27 build (e6c66a0bd4). I don’t have any idea what caused it. I never reported it, but I guess it would be considered a minor bug.

1 Like