Bug 508423

Summary:	Creating/adding a new color in palette crashes Krita
Product:	[Applications] krita	Reporter:	Unknown <null>
Component:	Dockers	Assignee:	Krita Bugs <krita-bugs-null>
Status:	RESOLVED DUPLICATE
Severity:	crash	CC:	nicholaslapointe8, santillanlancealec
Priority:	NOR
Version First Reported In:	5.2.11
Target Milestone:	---
Platform:	Microsoft Windows
OS:	Microsoft Windows
Latest Commit:		Version Fixed In:
Sentry Crash Report:
Attachments:	attachment-2589382-0.html

Description Unknown 2025-08-18 13:32:46 UTC

***
If you're not sure this is actually a bug, instead post about it at https://discuss.kde.org

If you're reporting a crash, attach a backtrace with debug symbols; see https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports

Please remove this comment after reading and before submitting - thanks!
***

SUMMARY
Creating a new palette crashes Krita. This even occurs with a fresh install via Toolbox, and when kritarc is removed.

STEPS TO REPRODUCE
1. Create a new palette with the palette docker

OBSERVED RESULT
Krita crashes.
gdb says:
```
Thread 1 "krita" received signal SIGSEGV, Segmentation fault.
0x00007ffff4cfab54 in KisSwatchGroup::columnCount() const () from /usr/lib64/libkritapigment.so.19
```
With krita-libs-debuginfo installed:

```
Thread 1 "krita" received signal SIGSEGV, Segmentation fault.
KisSwatchGroup::columnCount (this=this@entry=0x0)
    at /usr/src/debug/krita-5.2.11-1.fc42.x86_64/libs/pigment/resources/KisSwatchGroup.cpp:141
141         return d->colorMatrix.size();
```

EXPECTED RESULT
A palette is created.

SOFTWARE/OS VERSIONS

Operating System: Fedora Linux 42
KDE Plasma Version: 6.4.4
KDE Frameworks Version: 6.17.0
Qt Version: 6.9.1

ADDITIONAL INFORMATION

Comment 1 OwO the Deity 2025-08-30 11:08:26 UTC

Hi, the moment I add a new color into my palette, Krita stops responding and crashes all of a sudden. How can I fix this?

Comment 2 Nicholas LaPointe 2025-09-01 02:05:42 UTC

Thanks for your report! This bug is known and has been fixed for the next release of Krita.

*** This bug has been marked as a duplicate of bug 507601 ***

Comment 3 OwO the Deity 2025-09-01 03:37:49 UTC

Created attachment 184618 [details]
attachment-2589382-0.html

Hi, is the bug already fully fixed?

On Mon, 1 Sept 2025, 10:51 am Nicholas LaPointe, <bugzilla_noreply@kde.org>
wrote:

> https://bugs.kde.org/show_bug.cgi?id=508423
>
> Nicholas LaPointe <nicholaslapointe8@gmail.com> changed:
>
>            What    |Removed                     |Added
>
> ----------------------------------------------------------------------------
>          Resolution|---                         |DUPLICATE
>              Status|REPORTED                    |RESOLVED
>                  CC|                            |
> nicholaslapointe8@gmail.com
>
> --- Comment #2 from Nicholas LaPointe <nicholaslapointe8@gmail.com> ---
> Thanks for your report! This bug is known and has been fixed for the next
> release of Krita.
>
> *** This bug has been marked as a duplicate of bug 507601 ***
>
> --
> You are receiving this mail because:
> You are on the CC list for the bug.

Comment 4 Nicholas LaPointe 2025-09-02 03:18:22 UTC

(In reply to OwO the Deity from comment #3)
> Hi, is the bug already fully fixed?

I have not personally verified yet, but from my understanding, it has been fixed.
If you'd prefer not to wait for the next release (I'm not sure of when that will be), prerelease versions of Krita are available from https://cdn.kde.org/ci-builds/graphics/krita/krita-5.2/ and should contain the fix.