-
408443 – Input field on sliders don't lose focus when clicking outside of the input field
Re-confirmed for 5.2.6. -
442531 – Menus on 'Brushes and Stuff' toolbar are sticky.
Re-confirmed for 5.2.6 (thank you for the help @AhabGreybeard!) Seems to be specific to Windows. -
447891 – In the Comic Manager, when edit Exportation Parameters, cannot select a color for the layers to be removed
Re-confirmed for 5.2.6; there are now checkboxes that clarify selections, but the state of checkboxes aren’t initialized when opening the dialog. -
329663 – Do not allow conflicting shortcuts in "Configure Shortcuts" and "Custom Input Settings"
Re-confirmed for 5.2.6; longstanding and probably complicated issue. Setting the version to 5.2.6 just out of formality. -
359858 – Round pixel brush jagged when size is between 9 and 4.
Re-confirmed for 5.3 pre-alpha. -
419976 – c)_Pencil-3_Large_4B brush glitches on second picture
Resolved! -
447514 – New gradient smoothing is not applied to mesh gradients / Mesh gradients looking really blocky
Re-confirmed for 5.3 pre-alpha. Unfortunately lead to the discovery of a new bug… -
496519 – Editing handles of mesh gradient raises safe assert
New bug as of 5.3 pre-alpha.
I tested this with 5.2.3 and 5.3 alpha on Win 11 with non conflicting shortcuts. For me it works as expected - I added a corresponding comment to the bug tracker.
483731 - Drag and drop of color is always darker/different than the selected color
Reported for 5.3 alpha, confirmed with 5.2.3
466368 -Sketch engine at low opacity cannot fully over paint black color with white one
Confirmed with 5.3 alpha
https://bugs.kde.org/show_bug.cgi?id=434938
Reconfirmed on Windows with 5.2.6 and 5.3.0-alpha (3138bbd1)
https://bugs.kde.org/show_bug.cgi?id=363153
Reconfirmed on Windows with Krita 5.30-alpha (3138bbd1) and 5.2.6
As the mounth will soon be over, should we proceed to confirm more bugs? The ones confirmed already are maybe more than can be fixed in a month time I think.
Hi, all!
Today will be the last day of the Bughunt Month! I will still try to fix as much of the bugs you conifrmed as possible today!
Thank you very much @cgidesign, @prutser, @Reinold, @Vitamorus, @YRH, @wakocima, @AhabGreybeard, @BeARToys and others!
Together we have managed to reduce the number of bugs on bugzilla from 900 reports to 803 reports! Almost a hundred of bugs gone!
According to stats, during this month the testers team (re-)confirmed 40 bugs, 14 of which got momentarily fixed by developers! Almost 120 reports were closed as duplicates or “needsinfo”, which is a huge cleanup for bugzilla!
The developers team fixed 65 bugs in total, which is also a good progress: Krita now has 65 fewer issues! ![]()
The developers still have 33 recently confirmed bugs, so we have something to do for at least a month.
I hope we will be able to repeat such bugs-feasts regularly. For example: “A bughunt week every first week of the month” or “Two bughunt weeks every two months”. Do you like this idea? ![]()
PS:
If you like, you can still look into confirming bugs even outside the “bughunt” periods. I usually devote one day per week on fixing recently appeared bugs. If you confirm something new, I can fix it very quickly ![]()
100 bugs in a month, woo! Let’s keep this momentum going! ![]()
Although I think we all would like a Bughunt Year ever year, I personally think part of getting a bit of action going is to not make it too frequent. I would suggest maybe a goal of 4 bughunts weeks a year, and make it either once every quarter, 2 weeks every 6 months or 1 month per year. Just to keep it a special event rather than making it too mundane (a month goes by very fast!) and to not exhaust participants.
Hopefully there’s enough incentive to review and improve the resources and strategies used for the bug hunt as well. Things like a temporary dedicated page on the Krita website in place of the google document, a specific download page for “the official bughunt version of krita” to check against, seeing if the process can be streamlined in some fashion (e.g. the step of “declaring intention” on the forum thread was perhaps a bit superfluous), an introduction video hosted on the Krita youtube channel, and so on.
Quarterlies seem neat!! If it would help, I could try to offer some rewards; I had Krita charm designs already planned, so printing a few additional ones isn’t going to cost me an arm and a leg. It’s not much but I’d love to contribute in some way!
Outside of that, I hope to be more active in regards to bug hunts of my own. I’ve an odd talent for finding them in everything I touch, so helping the team in this regard seems like a good choice since I can’t help with fixing yet ( trying to understand all the Krita code on my own is… time consuming, to say the least
)
If you like, you can still look into confirming bugs even outside the “bughunt” periods
Will the links of the “high priority” bugs remain valid? In that case, I’ll try to make it a sort-of-regular thing (I don’t want to overpromise).
Yes, there is a script that automatically runs twice a day to update those links ![]()
Great! I’ll bookmark it ![]()
I think quarterly is a good cadence. I agree that if it’s it’s too often it loses a bit of specialness to get people to jump.
This one can be closed (not a bug but a user configuration missmatch):
I am not a developer, so I think I am not the right person to close the bug ticket.
But as I understand it, the user issue which was posted as a bug, is caused by this one:
https://bugs.kde.org/show_bug.cgi?id=329663
I just tested this with
krita-x64-5.3.0-prealpha-f043c4f9
Windows 11
Intel
Nvidia RTX
The issue happens there as well.
Thank you! I’ll try to check this bug next week! ![]()
The only bug I could think up I would like to see get worked on, is improving the animation camera capabilities in krita.
https://bugs.kde.org/show_bug.cgi?id=497392
Other than that, I think krita is doing great for me. ![]()
That is not a bug but a feature request, but okay, these are called “wish bug”.
Michelist