Bug? User error? (Windows) Some modules having no effect

Software darktable
1

Darktable 5.0, Windows
I did not see this on the previous release (4.9ish?)
Some of my modules are having zero effect. I am very much a “click it and see what happens” user of this software, and I am noticing that there are frequent instances where nothing happens! Contrast Equalizer and Diffuse/Sharpen are the two I see it happen with most often. The picture I attached (with XMP) is currently exhibiting this issue.
A simple example is:

  1. Contrast equalizer is default/inactive.
  2. I select “bloom”
    Expected: Contrast Equalizer becomes Active, and the bloom effect is applied.
    Actual: The module is not activated, and bloom is not applied.
    Manually activating the module and then selecting “bloom” does nothing.
    The “working” message appears briefly over the image.
    Restarting the app does nothing.

Update – It seems all my images are responding the same way…even an untouched raw. No bueno. It was off/on previously, but its finally just borked for everything.

Did I activate something that conflicts with these modules?

(Also, I need an adult to tell me those are lens flares, not northern lights)

P1310278 (2025_02_04 11_43_15 UTC).ORF (13.9 MB)
P1310278 (2025_02_04 11_43_15 UTC).ORF.xmp (17.1 KB)

NightShot
NightShot1920×1413 297 KB

This file is licensed Creative Commons, By-Attribution, Share-Alike.

2

I downloaded your image and xmp file. The xmp file appears to be the incorrect one for this image as the name has got jpg in it. Also, I am on Windows 11 using DT 5.1.0 +239 and cannot replicate any problems using the contrast equalizer module.

EDIT: I changed jpg to ORF in the xmp file name and it applies the bloom option from the contrast equalizer module correctly on my DT 5.1 install.

3

  1. Fixed my xmp. Sorry.

  2. DT 5.0.1 was released the day I posted this. I check frequently, but apparently not frequently enough.
    After upgrading, its working fine. I dont see in the release notes where this is called out, but there were a lot of fixes listed.
    Cache cleanup? Bugfix? We shall see!

Thank you for taking the time to look at this @Terry