Error: Colour policy not yet initialised

Flame Flame Questions
1

On 2025.2.5 on rocky, (not sure which version). 2023. I constantly getting the above and have to restart both wiretap services to fix it.
Anyone else see this? have a fix for it?

2

Nobody?

3

We did have this problem especially on machines running long without restart. Restarting services is the only solution when it happens but overall can be caused by a few things. Gonna be in front of a machine in a few hours I will check cfg paths because I donā€™t remember them of the top of my head :joy:

4

Itā€™s really doing my head in, Iā€™m having to restart services sometime 3x in succession to get it to work.
The box Iā€™m on also has 2023 on it, however, all running services appear to be 2025.

5

Just checked and this is what services are running.
Any thoughts?

flame 2
flame 21792Ɨ446 80.8 KB

6

to find out which version of rocky linux:

open a terminal

uname -r

youā€™ll get a response like this:

[root@echo ~]# uname -r
5.14.0-611.16.1.el9_7.x86_64

where 9_7 is the version of rocky linux

you probably need to tidy up the version mismatches in your services which probably means ā€˜letting goā€™ of 2023, and upgrading your projects to a newer version.

7

Thanks Phil, Iā€™ll check tomorrow but as Iā€™m freelance, Iā€™m not sure they can dump 2023

8

Rocky 8.5

9

Iā€™m still suffering badly with this, but need to have both 2023 and 2025 on the system.
Is there no fix for it?

10

Dual boot may benefit you in this scenario if you need to keep 2023 up and running and are having issues with an unsupported OS. You could install Rocky 8.5 on a secondary drive for 2023, use BIOS to boot to the intended drive and call it a day.

11

We are on 2025.2.x, and even that feels ancient, yet necessary given the ridiculousness of 2026+, but ā€œneedingā€ to stay on 2023 is just foolish.

Also, 2025.2.5+ works fine on RockyLinux 9.7, and that is what we will probably be on until ā€œThe Collapseā€ which is closer everyday.

12

I find cat /etc/os-release to be easier and clearer.

13

Foolish it may be, and I canā€™t speak for Paul, but this is usually dictated by the client, not the artist who has no say in the matter.

14

I got the same error when I got a new machine and loaded projects in full from archive. I copied my colour policy from the old machine to /opt/Autodesk/shared/colour_mgmt/configs, then opened the project management window, selected my_project>manage, toggled the blue pop-up next to OCIO Config from Keep Current Preferences to Use a Preset and loaded my preset.

15

Helpful as ever Alanā€¦

16

I have suggested that

17

Itā€™s a peculiar situation that anyone other than the flame artist gets to decide the version of softwareā€¦

Sighā€¦