Edited brushes that we save / overwrite disappear from the Brush presets STEPS TO REPRODUCE 1. Use the x64 portable version on Windows 10 2. Select a brush 3. Resize the Brush 4. Overwrite and Save new Brush Preset OBSERVED RESULT Now, the brush has disappeared. You can saw it in the "Brush Preset History", but it is not on the "Brush Presets" any more EXPECTED RESULT - The brush should be overwrite and kept in its actual preset - If saved, the saved Brush should be a copy stocked in the same preset SOFTWARE/OS VERSIONS Windows 10 Pro ADDITIONAL INFORMATION Used software version: Krita 4.4.0 Portable for Windows x64 (I also noticed that bug for all the previous versions since Krita 3)
Do you have a tag selected in the Brush Presets docker? Because if you save or overwrite a brush, it doesn't inherit tags, so it "disappears" from the tags-filtered view. (It's a bug but a known one).
(In reply to Tymond from comment #1) > Do you have a tag selected in the Brush Presets docker? Because if you save > or overwrite a brush, it doesn't inherit tags, so it "disappears" from the > tags-filtered view. (It's a bug but a known one). Hello Tymond, Well, I can't retry right now because my computer suddenly suddenly broke down some days ago, so I need to wait to buy new hardwares to confirm, but from my memory, I'm quite sure that I tried with and without a tag selected... I'll confirm once I get my new PC, probably in December.
Thanks for your comment! Automatically switching the status of this bug to REPORTED so that the KDE team knows that the bug is ready to get confirmed. In the future you may also do this yourself when providing needed information.
Hello and sorry for the late reply. I confirm, I tryed to select a tag in the Brush Preset Docker before overwriting, and I still have the same issue. The Brush totally disappears from any Brush Preset. I can ONLY find it again in the "Brush Preset History"... at the condition, I guess, that I don't use too many other brushes before trying to reuse that one.
*** This bug has been marked as a duplicate of bug 391025 ***