Bug 344142 - Changing the Advanced color selector resets OCIO config
Summary: Changing the Advanced color selector resets OCIO config
Status: RESOLVED WORKSFORME
Alias: None
Product: krita
Classification: Applications
Component: Color Selectors (other bugs)
Version First Reported In: git master (please specify the git hash!)
Platform: Other Linux
: NOR normal
Target Milestone: ---
Assignee: Krita Bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-02-14 01:42 UTC by Jonathan Ringstad
Modified: 2020-03-20 04:33 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Jonathan Ringstad 2015-02-14 01:42:44 UTC 
Setting up the OCIO docker to e.g. use "View: sRGB" and then switching the color-selector resets the OCIO docker to "View: None".

Tested with a recent build of the calligra/2.9 branch.

Reproducible: Always

Steps to Reproduce:
1. Set up OCIO with some view value other than "none"
2. Switch color selectors

Actual Results:  
Resets the view

Expected Results:  
Should probably not reset.
Comment 1 Halla Rempt 2015-02-14 08:57:01 UTC 
Hi Jonathan,

I can confirm the behaviour. I'm not sure though why it happens...
Comment 2 Jonathan Ringstad 2015-02-14 10:53:45 UTC 
It seems that quite a few things make the OCIO docker reset, like converting the colorspace, turning OCIO on/off, et cetera.
Comment 3 mvowada 2018-04-30 08:09:18 UTC 
(In reply to Jonathan Ringstad from comment #2)
> It seems that quite a few things make the OCIO docker reset, like converting
> the colorspace, turning OCIO on/off, et cetera.

I can confirm the same behaviour in "Krita 4.1.0-pre-alpha (git 2e8cf39)" - Ubuntu 14.04.
Comment 4 amyspark 2020-02-19 20:03:55 UTC 
I have tried to reproduce this to no effect in master (https://invent.kde.org/kde/krita/commit/dffa076018d6bf98ec0e3d7c232dc2825fd47c11).

Can anyone else check if this behavior still happens?
Comment 5 Bug Janitor Service 2020-03-05 04:33:11 UTC 
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 6 Bug Janitor Service 2020-03-20 04:33:13 UTC 
This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!