https://bugs.kde.org/show_bug.cgi?id=506291
--- Comment #5 from Noel Santos <[email protected]> --- (In reply to Halla Rempt from comment #4) > On a system where you can reproduce the crash, could you temporarily reset > Krita's settings by moving .config/kritarc to .config/kritarc.bak and check > whether it still happens? If it doesn't then we'd have to take a look at the > broken kritarc file. I did some testing and narrowed down the steps to reproduce the bug. 1. It happens even with the default kritarc 2. It happens even when the gradient is button is working normally 3. It doesn't happen if you apply the filter to a transparent layer 4. It happens when you apply the filter to the white background layer that is locked by default--you have to unlock it first, of course. 5. It doesn't happen if the background layer is black or red. I didn't test every color but it seems it only crashes with white background. 6. It doesn't need to be the background layer Krita creates for you, you can make a new paint layer, shift+backspace to fill it with white, and then it will crash. Now I can reproduce it with any user on my machine. The reason I wasn't able to before was because by default Krita creates a white background layer and a transparent layer and the transparent layer was selected by default. Applying the filter to the white background layer crashes Krita. Considering it only crashes with white background and not other colors, there's probably a bug in the index colors algorithm rather than on the UI. -- You are receiving this mail because: You are watching all bug changes.
