Bug 502957

Summary:	Save and restore custom colors
Product:	[Applications] kcolorchooser	Reporter:	Claire <accounts>
Component:	general	Assignee:	Unassigned bugs <unassigned-bugs-null>
Status:	CONFIRMED ---
Severity:	wishlist	CC:	andrew, balazs, clesioteixeira, fausto.nunez, nate, welcomebacktomyreality
Priority:	NOR
Version First Reported In:	25.04.2
Target Milestone:	---
Platform:	openSUSE
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:
Bug Depends on:
Bug Blocks:	509881

Description Claire 2025-04-18 04:42:48 UTC

SUMMARY
The custom colors I had saved wiped. No problem, I figured I'd just set them back up. Do so, then click okay. Open kcolorpicker again and -- well, the colors are gone again. 

STEPS TO REPRODUCE
1. Add a bunch of custom colors
2. Click okay on KColorChooser
3. Relaunch KColorChooser

OBSERVED RESULT
All custom colors reverted to #ffffff

EXPECTED RESULT
My color schemes should probably save.

SOFTWARE/OS VERSIONS
Operating System: Arch Linux
KDE Plasma Version: 6.3.4
KDE Frameworks Version: 6.12.0
Qt Version: 6.9.0
Kernel Version: 6.14.2-arch1-1 (64-bit)
Graphics Platform: Wayland
Processors: 16 × AMD Ryzen 7 5800X3D 8-Core Processor
Memory: 31.2 GiB of RAM
Graphics Processor: NVIDIA GeForce RTX 2060 SUPER

Comment 1 fausto.nunez@mailbox.org 2025-06-29 09:15:03 UTC

I can reproduce this issue on NixOS with KDE Plasma 6.4.1 and Qt 6.9.0.

Using `strace` to monitor file access, kcolorchooser only reads configuration files but never writes when saving custom colors. The application shows no `write()` system calls to any config files during the save operation.

Custom colors persist within the current session but are lost on restart because they're never written to disk. Previously I was able to manually edit ~/.config/QtProject.conf to customize the palette, but that no longer works as kcolorchooser appears to ignore Qt's standard custom color configuration.

**Expected:** Custom colors should be saved to `~/.config/QtProject.conf` or KDE config files.  
**Actual:** No configuration data is written anywhere.

This appears to be a missing save implementation rather than a file permission or path issue.

Comment 2 welcomebacktomyreality 2025-07-03 04:24:37 UTC

I'm experiencing the same behavior after updating on Mint; custom colors saved previously are gone & no longer saving after application closes. Been using this software very frequently recently & issue occurred immediately after only updating the program.

Version: 25.04.2
OS: KDE Flatpak runtime 6.9 (x86_64)

Comment 3 TxTechnician 2025-09-07 05:51:09 UTC

I've had the same problem since July.  

As of now I'm search of just manually configuring the custom colors.  But the color picker doesn't appear to load any data when It is called.  Happens globally, no matter the app (spectacle, kcolorchooser, etc).  Anything that uses QtColor.

Comment 4 Nate Graham 2025-09-10 06:50:56 UTC

*** Bug 507963 has been marked as a duplicate of this bug. ***

Comment 5 welcomebacktomyreality 2025-09-15 06:02:43 UTC

Switched to system package of KColorChooser for Linux Mint Xfce & it works there. Version 21.12.3  
  
Flatpak version still not working: Version 25.08.1