Linux Mint users, let's try crashing Krita with the Index Colors filter

Develop Artists Feedback & Testing
1

Hi. If you use Linux Mint and the appimage (5.2.9 to nightly), can you try to crash Krita for me so this bug can be confirmed? Steps:

  1. Open a new document in krita.
  2. Filter → Artistic → Index Colors.
  3. Uncheck Bright, Light, and Base in this order.

After a few moments, Krita should crash. If it doesn’t crash, do tell because that means it crashes for some other reason.

Thanks. :slight_smile:

1 Like
2

i tested with 5.2.9 appimage on my linux mint 21.3 cinnamon but did not crash, was able to turn the layer black for me. i’ve followed exactly as your video’s layer setup, performing the filter on the sole background layer. My document settings is 7016px by 4961px, 600ppi, RGB 8 bit with the default icc profile.

1 Like
3

Oh no. I guess it only crashes on my machine then. I wonder why…

I have also managed to crash Krita by enabling gradient overlay, and other people weren’t able to reproduce it. At that time I switched to a different user and tried reproducing it, and I couldn’t. My assumption at the time was that gradient overlay was crashing because somehow the gradient on my toolbar didn’t have any gradient selected. I don’t know how I managed to do that, but I figured if someone else managed to get Krita in that state it would probably crash gradient overlay.

So this time I tried switching to a different user on my machine too, and it turns out I can’t get it to crash on a different user this time either! Maybe my main user is just cursed? Why do I only find these crashes when I’m using Krita normally…

Anyway, this means that it isn’t a hardware issue that causes the crash but some user-level configuration or the current state of the application that is loaded from the last use that is required to crash Krita this way. I have no idea why Index Colors would be using state outside the dialog, but that’s the only reason I imagine for a crash to happen with one user profile but not with a different user profile in the same machine.

Does anybody know how to make the gradient button become empty on purpose? I feel like that could be the bug that is making all these bugs happen on my machine.
image

4

ooh the missing gradient button definitely may be a cause. does your different user have the missing gradient button as well? I have no idea how to make it missing, if i remove the gradient button manually from my toolbar it would not leave an empty space.

5

Go to ~/.config/ and rename kritarc to kritarc_backup, and then try again.
Then If it crashes, add the original kritarc file to the bug report.

6

Hey. I’ve tried to diff it myself and I couldn’t figure out where the current gradient is set. I did find something interesting, though!

If you create a new tag in gradients and select a gradient in it, when you reload Krita the gradient will be undefined. In my case I had made a “Basic Gradients” tag and added “Black to White” to it.

image
image299×415 12.3 KB

I think this may be the bug. Can someone try confirming it?

1 Like
7

ooh i can replicate the missing gradient bug with your instructions. but no crashes when unchecking bright, light then base using index colors.

8

Interesting. By the way, are you using the filter on a transparent layer or on a white background layer? I’ve managed to reproduce the bug with a default kritarc, but it only happens if you apply the filter to the white background layer that is locked by default instead of the transparent layer. Perhaps that’s why others haven’t managed to reproduce it?

9

white background layer, there’s nothing to filter if the layer is transparent.

1 Like