Whitebalance shift while setting exposure

Is there an existing issue for this?

• I checked and did not find my issue in the already reported ones

Describe the bug

On darktable 5.4.0, while I was using the none auto-apply pixel workflow default option, if I use the color calibration module as auto, and then set the exposure, the white balance is shifted towards blue. If exposure is manually assigned, or if the module is reset, the issue is reverted, until a new operation is done.

This seems to happen if the area for auto adjusting in the white balance is left active.

Steps to reproduce

1. Ensure the White Balance is in "as shot to reference"
2. On color calibration, use the dropper to set the white balance without modifying the area.
3. On exposure, use the area selector eyedropper to choose the area. The white balance shifts to blue.
4. Manually set the white balance. The blue shift is cancelled.

Expected behavior

darktable should keep the white balance settings.

Logfile | Screenshot | Screencast

No response

Commit

No response

Where did you obtain darktable from?

darktable.org / GitHub release

darktable version

5.4.0

What OS are you using?

Windows

What is the version of your OS?

Windows 11 Pro

Describe your system

32 GB RAM, AMD Ryzen 7 8700G, RTX 4070 Super, x870 MOBO

Are you using OpenCL GPU in darktable?

Yes

If yes, what is the GPU card and driver?

ASUS RTX 4070 Super with Game Ready driver ver. 591.74

Please provide additional context if applicable. You can attach files too, but might need to rename to .txt or .zip

So far, I have only experience it with Nikon Z8 Raw Files. After discarding history, the issue seems to not happen for some time.

Reproduce the issue in darktable 5.4.0 using a Nikon Z8 RAW file, focusing on the White Balance, Color Calibration, and Exposure modules. Follow the listed steps and verify that selecting an exposure area no longer shifts white balance toward blue while the white balance remains unchanged.