Created attachment 183155 [details] LastCrash SUMMARY I just wanted to change the Advanced Color picker to LAB Mode. STEPS TO REPRODUCE Start Krita (Windows, Steam version 5.2.10). Open Settings → Configure Advanced Color Selector Settings. Enable Custom LAB color space (e.g. L*A*B). Confirm the selection—Krita shows the selector briefly, then crashes hard. After that, Krita will not start again unless the config is reset. OBSERVED RESULT After confirming the custom LAB setting, Krita crashes after some secounds. On restart, Krita doesn’t open at all—a splash, but no window. Deleting the Part [advancedColorSelector] in kritarc, reset the configuration for the colorpicker. And Krita starts normal again. EXPECTED RESULT The Advanced Color Selector should apply the chosen LAB config without issues. Enabling/disabling custom LAB should work safely via the UI. SOFTWARE/OS VERSIONS Windows: Windows 10, (Steam Krita 5.2.10) ADDITIONAL INFORMATION Product: Krita Version: 5.2.10 (Windows, Steam) Component: Color Selectors (Advanced Color Selector) Platform: Microsoft Windows 10 Steam installation. Reproducibility: Probably reproducible, im not touching that setting again. attachment of last Crashlog (of a starting attempt)
Hello! Sorry for the late response. I'm not able to cause this crash on my Linux device, but I might be missing something. Are you trying to set the color space to trying to change it to the built-in "Lab identity" profile, or are you trying to use a custom colour space profile that you created/downloaded yourself? If it's the latter, could you please attach the profile you're trying to import? Krita recently got a sort-of-successor to the Advanced Colour Selector called the Wide Gamut Colour Selector. Could you try doing the same with the Wide Gamut one and see if the crash still happens?
🐛🧹 ⚠️ This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information, then set the bug status to REPORTED. If there is no change for at least 30 days, it will be automatically closed as RESOLVED WORKSFORME. For more information about our bug triaging procedures, please read https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging. Thank you for helping us make KDE software even better for everyone!
🐛🧹 This bug has been in NEEDSINFO status with no change for at least 30 days. Closing as RESOLVED WORKSFORME.
(In reply to Vitamorus from comment #1) > Hello! Sorry for the late response. I'm not able to cause this crash on my > Linux device, but I might be missing something. > > Are you trying to set the color space to trying to change it to the built-in > "Lab identity" profile, or are you trying to use a custom colour space > profile that you created/downloaded yourself? If it's the latter, could you > please attach the profile you're trying to import? > > Krita recently got a sort-of-successor to the Advanced Colour Selector > called the Wide Gamut Colour Selector. Could you try doing the same with the > Wide Gamut one and see if the crash still happens? No i didnt change the colorspace of the document, i just wanted to test the Buildin Lab setting only for the Colorpicker. No i didn't download a custom colorspace for the picker or the document, it was the one that comes with. After selecting the colorspace in the UI and press applied, Krita crashed without warning shortly afterwards (possible after the advanced colorpicker updates). After restarting Krita, it continues crashing. Reseting the Config manual (deleting the changes to the advanced colorpicker). Krita start normal again (with the usual standart colorspace on the colorpicker and reseted settings) Im not sure if this is a linux problem, as i use the steam windows version.