[volunteers needed] Krita Bughunt Month Started

Develop Artists Feedback & Testing
23

A post was split to a new topic: Can’t set XP Pen tablet buttons

24

3 posts were split to a new topic: Question on multi-brush tool

26

Hi, all!

Just a small heads-up:

The bughunt is still running! During the last 20 days we have fixed 66(!) bugs! We have also triaged 33 additional bugs and put them into NEEDSINFO state! So, we are running really well, Krita is now at the level of 826 bug reports :slight_smile:

It is a bit sad that I had to skip one week of the bughunt, because of recovering the Android packages. But now I’m fully back and ready to fight against the bugs!

Now we have 10 days left and we have only 16 recently-confirmed bugs left in the document, so I might run out stuff to fix very soon. It would be nice if you could triage more bugs for me! :slight_smile:

4 Likes
27

Hi, @wakocima!

Could you give me some hint about clone tool bug? I still cannot reproduce it here locally.

28

Triaged some bugs:

  • 434916 Not preserving metadata information in png and kra formats (have not tried other formats)

    • Confirmed only for png. .kra files do properly save/load author info but .png Krita doesn’t save/load the author information at all.

  • 434655 pop up color selector not always fully on screen

    • confirmed. Added some screenshots to help show the behavior

  • 475107 Crash when exiting Canvas Only mode while toolbar is expanded

    • Confirmed. Strangely seems only reproducible on brand new files

  • 356462 Conversion from integer to float and back gives rounding errors for opacity

    • Re-Confirmed from 2016
1 Like
29
3 Likes
30

and a couple more, just for fun.

3 Likes
31
5 Likes
32

Re-confirmed bugs

Re-confirmed non-bugs (probably)

Resolved / Needs info

5 Likes
33
2 Likes
34

Hi, @Reinold and @Vitamorus!

Thank you a lot for the help with triaging bugs! I just followed your changes on bugzilla and fixed recently-confirmed bugs! This way together we have managed to fix at least 12 bugs this week :slight_smile:

I have also fixed two other bugs, but I need some testing from people before I merge the changes:

I have started separate threads for them. The second patch is for the bug confirmed by @Reinold (356462 Conversion from integer to float and back gives rounding errors for opacity) :slight_smile:

4 Likes
35

A quick bug report, if I may (version 5.2.6).

If there’s a layer with a mask, that mask can be moved to another adjacent layer with a mouse drag or a shortcut combination like Ctrl+PgDown.

If the keys are used, it’s possible to move the mask into the locked layer, thus modifying that layer. Here’s an example with the default new document:

image
image390×400 10.4 KB

Select the transparency mask and Ctrl+PgDown:

image
image396×399 10.6 KB

36

I am not in an official tester team.

Nonetheless checked this bug: 485590 - Some windows don’t show on the same screen as Krita is open on.

It is still there in 5.2.6 and 5.3 alpha on Windows.
I can confirm it happens as described but not if it is considered a bug (I would call it a UX bug but technically it works → e.g. F5 opens the brush settings as expected but on the wrong monitor).

Should I change the state to “Confirmed”?

Here is another one - that one I can’t reproduce. It works as expected in 5.2.6 and 5.3 alpha.
485717 - Layer opacity not working

3 Likes
37

@YRH
Thank you for bringing this to light!
This does seem to be a bug since Krita stops every other way of moving a mask to and from a locked layer. Would you mind filing a bug report on https://bugs.kde.org/ so that the devs have it in the tracker? If you then DM the report to me (or link it in this thread) I can confirm the bug right away.

@cgidesign
(The teams aren’t really registered afaik, if you wanna help out confirming bugs then all the information is in the google document dkazakov posted up top)

485590 - If you can reproduce it in the latest official release (5.2.6 as of writing moment) and/or the 5.3 pre-alpha you can go ahead and change the Krita version in the bug report to the version you tested at set it to confirmed :slight_smile:

485717 - If you can’t reproduce the bug in a current version of Krita then you first check if you can reproduce it in the version stated in the bug report (in this case 5.2.2).

  • If you CAN reproduce the bug in the old version but NOT a newer version, then the bug has resolved itself and can be labeled as ‘resolved fixed’.
  • If you CAN’T reproduce it in either version you label it as ‘needsinfo waitingforinfo’ and ask the reporter if they can confirm the bug is still around and if they can provide more info (better steps to reproduce, maybe screenshots or a video showcasing it, etc.).

Again, more info and all the instructions are in the document in dkazakov’s original post :wink: your help is appreciated!

3 Likes
38

477753 - Cursor and stroke delay on transparent (empty) canvas at the end of each stroke

Confirmed in 5.2.6 for Direct3D 11 via Angle - no issue with OpenGL.
(I had issues to add the screen recoding to the kde bug-tracker, so there are a few trial and error comments)

5 Likes
39

Hi @Vitamorus , I just took a stab at fixing the bug directly here:

Don’t allow lowering/raising a mask into a locked layer (!2273) · Merge requests · Graphics / Krita · GitLab

2 Likes
40

Thanks, @YRH! I’ve just merged your fix! :slight_smile:

4 Likes
41
3 Likes
42
4 Likes
43
2 Likes