https://bugs.kde.org/show_bug.cgi?id=391325

--- Comment #6 from Isaac <isaacnor...@live.com> ---
(In reply to Quiralta from comment #5)
> Modifying a brush "should" create a blacklist file, the problem I've seen in
> your case is that is omitting (in the blacklist) to append the word "backup"
> at the end, e.g. erasers.kpp > eraser_backup_2018_03_04.kpp
> 
> Modifying a brush also makes an actual copy/copies of the brush in the
> "paintoppresets" folder (an incremental backup practically).
> 
> I myself can not reproduce you issue, thus I wonder if it has to do with the
> windows build as like mvowada I'm also on Linux, for what its worth you
> should clean not only the blacklist but all the brushes (and its copies)
> that you are SURE don't need from the "paintoppresets" folder (if unsure
> just back up the folder) and try again, just to see that the names are not
> interfering.

I used used disk cleanup, CCleaner and Bleachbit to nuke my computer of all of
Krita-related files, the temporary folders, the program folders, registry
entries (everything of that nature), so that there can be absolutely NO
conflictions this time, and this was the result:

https://drive.google.com/file/d/1ofGPNvIKrmQw4g-wbt9zjx_GUuXs19F-/view?usp=sharing

You can see that I followed through with that, as you can see most of the
brushes I had in the other videos are missing, the UI looks like it does when
you wipe the %appdata% folders, and so forth. Yet, the issue still remains...
Notice how the file is created EXACTLY when I save changes to the newly-created
brush...

So, is it safe to assume that Micro$oft did something with this upcoming
version of Windows 10 that Krita just does not like?

-- 
You are receiving this mail because:
You are watching all bug changes.

Reply via email to