QA panel only module layout messes up on preset selection

[micharambou]

Describe the bug

A QA panel only module layout get's messed up each time the corresponding preset is selected. "Messed up" means: the custom QA Panel doesn't appear and looking at the module layout manager it looks like each added distinct module element becomes duplicated.

Steps to reproduce

1. in darkroom switch to module layout manager
2. created a new layout
3. remove all module groups in newly created layout except QA panel and remove/add any abitary module element (for example sigmoid: contrast)
4. close module layout editor and select newly created module layout
5. in module layout manager notice the duplication of added module elements

Expected behavior

QA Panel only module layouts should be useable

Logfile | Screenshot | Screencast

michael@manjaro-ws darktable]$ /opt/darktable-master/bin/darktable --version
darktable 753a3cd
Copyright (C) 2012-2024 Johannes Hanika and other contributors.

Compile options:
  Bit depth              -> 64 bit
  Debug                  -> DISABLED
  SSE2 optimizations     -> ENABLED
  OpenMP                 -> ENABLED
  OpenCL                 -> ENABLED
  Lua                    -> ENABLED  - API version 9.3.0
  Colord                 -> ENABLED
  gPhoto2                -> ENABLED
  GMIC                   -> ENABLED  - Compressed LUTs are supported
  GraphicsMagick         -> ENABLED
  ImageMagick            -> DISABLED
  libavif                -> ENABLED
  libheif                -> ENABLED
  libjxl                 -> ENABLED
  OpenJPEG               -> ENABLED
  OpenEXR                -> ENABLED
  WebP                   -> ENABLED

See https://www.darktable.org/resources/ for detailed documentation.
See https://github.com/darktable-org/darktable/issues/new/choose to report bugs.
[michael@manjaro-ws darktable]$ 

[michael@manjaro-ws darktable]$ /opt/darktable-master/bin/darktable 
    58.1790 [dt_action_locate] action 'QA_base' doesn't exist
    58.2011 [dt_action_locate] action 'QA_base' doesn't exist

Commit

No response

Where did you obtain darktable from?

self compiled

darktable version

753a3cd

What OS are you using?

Linux

What is the version of your OS?

Manjaro Linux

Describe your system?

Operating System: Manjaro Linux KDE Plasma Version: 6.1.3 KDE Frameworks Version: 6.4.0 Qt Version: 6.7.2 Kernel Version: 6.8.12-3-MANJARO (64-bit) Graphics Platform: Wayland Processors: 16 × AMD Ryzen 7 5800X3D 8-Core Processor Memory: 31.3 GiB of RAM Graphics Processor: NVIDIA GeForce GTX 1060 6GB/PCIe/SSE2

Are you using OpenCL GPU in darktable?

Yes

If yes, what is the GPU card and driver?

NVIDIA GeForce GTX 1060 6GB/PCIe/SSE2

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

No response

[github-actions[bot]]

This issue has been marked as stale due to inactivity for the last 60 days. It will be automatically closed in 300 days if no update occurs. Please check if the master branch has fixed it and report again or close the issue.

[ralfbrown]

Confirmed with current master. With a fresh config, removing all of the module groups and then selecting the new preset results in showing the active modules tab. Adding back a single module in a new tab gets the QAP, active modules, and new tab.

I noticed that every time my mouse pointer moves over the preset's name in the menu, I get an "action doesn't exist" error in the terminal for that preset, but this is a separate problem as it occurs for any user-defined preset.

[github-actions[bot]]

This issue has been marked as stale due to inactivity for the last 60 days. It will be automatically closed in 300 days if no update occurs. Please check if the master branch has fixed it and report again or close the issue.