Palette docker breaks imported Photoshop .act palette upon re-launch

There are a series of bugs I’ve discovered when doing community support:

  1. Krita won’t save imported Photoshop .act palette. It will drop any imported .act palette upon re-launch.

  2. Krita will break an imported Photoshop .act palette upon re-launch if it was embedded in a .kra file. The said palette is kept, but completely glitched out.

  3. When importing a palette, Krita will ask “Do you want to store this palette in your current image?”, if you choose “No”, Krita won’t import the palette, but loads “Swtch CMYK” palette.

  4. When importing a palette, Krita will ask “Do you want to store this palette in your current image?”, no matter which you choose, Krita will always set the value as “Document” in Palette docker’s “Folder” icon (Edit this Palette) dialogue.

Workaround for importing Photoshop .act palette in Krita:

  1. Import a .act palette
  2. Store in current image - Yes
  3. Export the imported palette as .kpl
  4. Load the .kpl palette
  5. Re-launch and it’s still there.

I’m pretty sure these are all legit bugs, probably unknown. But I will follow the instruction to post them here first. What should I do next?

This is the Photoshop .act palette file a community member sent me:
https://tysontan.com/temp/1111.act

Apparently there was a bug that marked as FIXED but actually still unfixed:
https://bugs.kde.org/show_bug.cgi?id=343115

I have reported the information there. Thank you for your time.

1 Like