Profile cover photo
Profile photo
RJ Quiralta
136 followers -
Traditional and Digital Illustration.
Traditional and Digital Illustration.

136 followers
About
Posts

Post has shared content

Post has attachment
Last doodle I did with #krita (master-branch = 4.1.x) : )

Post has attachment

Post has attachment
Indigenous Punk drawings - 10 of them, in no specific order :D

#pencil #ink #ballpen #art #illustration #fashion #quiralta
PhotoPhotoPhotoPhotoPhoto
5/13/18
10 Photos - View album
Add a comment...

Post has shared content
Right after we released 4.0.2, we found a regression where copy/paste would sometimes cause a crash. We fixed and some other things, and here's Krita 4.0.3: https://krita.org/en/item/krita-4-0-3-released/

Post has attachment
Didn't realize my gpu was dropped from the current nvidia driver, for those who find themselves unable to boot into graphic enviroment after the 396 update, better check the list.

Post has shared content
We just released Krita 4.0.2: the second bugfix release. See https://krita.org/en/item/krita-4-0-2-released/ for all changes!

Post has shared content
We;'ve just released Krita 4.0.1, the first bugfix release with over fifty bug fixes! See https://krita.org/en/item/krita-4-0-1-released/ for a full list and downloads.

Post has attachment
I'm about to start a new painting (for virtual machines) but just before starting I realized it would be good to do a quick study of the reference picture, thus this quick drawing, what I have in mind for the actual painting will be completely different :D

#krita #art #illustration #fashion #quiralta
PhotoPhotoPhotoPhotoPhoto
4/6/18
7 Photos - View album
Add a comment...

Post has attachment
RE: +Dušan Vukasović No problem, asking questions (regardless of type) is always the smartest thing to do :)

Reporting bugs is not complicated, although it takes some trial and error to figure whether the problem is a real bug or whether it belongs to Krita or any other software component of your PC. Thus the first step is to compare, if you notice that other users regardless of hardware experience the same, that's a sign of possible error in the code (bugs).

Thus:

Q1: Indeed, that's the website, you can even access it directly from Krita (help menu). When you browse the site, the bugs that are already fixed are kind of hidden for organization sake, but you can look for them explicitly. The amount of bugs is relative, as many reports are not correct. (many at times people misunderstand what this site is for and use it for general communication). But there is always something been reported, and there are but a handful of people to check and many less to fix, and undesired accumulation takes place. Thus the importance of "double checking".

Is a good practice to search for similar reports before doing one, still once you start a report, the site will display a list of bugs that the search engine "thinks" are similar or the same, thus you still have a chance to find out if you are making a duplicated report, this although not totally accurate, helps to diminish workload.

Q2: This is very important, it doesn't matter what operative system and hardware you use, you need to specify it, many bugs are left in "limbo" because they don't have this information, and thus makes it difficult to track and triage. In the form you fill, there are predefined menus where you can state the basics of your hardware/software, and the main window text is for demonstrating the steps to reproduce the error, links to videos, links to relevant information (like similar bugs), you can also attached images to show a visual problem. Thus don't leave information out, there is no need to over complicate though, just stay with the basics. If you miss a detail, you likely will be asked to mention it.

Q3: The developers are constantly (every day) fixing something on the code, for those who build krita (like I do) they have the newest possible every day, using "alpha", "beta", "nightly", will add the fixes that are already implemented, for those using the stable release, they can give these newer version a quick try and see if the problem has been fixed already or if still persist, this helps quite a bit since it will give developers a much better "frame" of the problem and will avoid reporting a bug that has been cleared out.

Note that the stable release is a static version, doesn't change anything until you move to the next stable version. No fix can be retrofitted to these versions, thus a bug in e.g. Krita 4.0.0, will forever stay in that version, the fix will then be in 4.0.1, 4.0.2, 4.1.0, etc.

Q4: There are no levels of reporting, everyone can help on triaging, is as simple as reproducing the bug in (first) similar or same hardware/system, and also on any. If you can reproduce the bug you can simple make a comment and specify your details (including hardware/system), other more advance user or the devs can then change the status of the bug, there is also finding duplicated bugs and "merging" them. Commenting in a bug with correct details and data (as simple as "I can reproduce this bug in my windows7 with my wacom tablet on the same version of Krita") help the devs to figure that more than one person can experience the problem. If the bug is already confirmed, there is no need to comment on it, unless is your own report and you want to add additional information.

To keep track of fixes, devs link the fixes and changes in the code, as a user you will see like odd numbers and symbols along comments, it means something has been done to that specific bug, for the user there is nothing to do with it, is either wait for the next release of Krita or try a nightly build/beta the check. At times if time permits, a dev will also let you know that the fix was done in a comment and invite you to try an unstable version, this is to verify that the fix works across systems.

All in all, is a simple method, what it takes time is to figure whether is a Krita bug or user error/other component bug. after that the rest is pretty straight forward :)

Quick guide/notes : https://plus.google.com/+CriolloakaRJQuiralt%C3%A6/posts/bpnGYuBkHho
Wait while more posts are being loaded