Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Module presets not applying after upgrade 4.8 to 5.0 #18184

Open
mprichards opened this issue Jan 10, 2025 · 11 comments
Open

Module presets not applying after upgrade 4.8 to 5.0 #18184

mprichards opened this issue Jan 10, 2025 · 11 comments

Comments

@mprichards
Copy link

Describe the bug

None of the presets on modules work when selecting them from the hamburger menu. I have tried creating my own preset and these do not work either. Were working fine prior to upgrade.

Steps to reproduce

  1. Open image in darkroom
  2. Select module preset (eg diffuse or sharpen: sharpness)
  3. Module stays inactive, no changes applied

Expected behavior

Presets should activate module with expected values

Logfile | Screenshot | Screencast

No response

Commit

No response

Where did you obtain darktable from?

downloaded from www.darktable.org

darktable version

5.0.0

What OS are you using?

Windows

What is the version of your OS?

Windows 11 Pro

Describe your system?

No response

Are you using OpenCL GPU in darktable?

Yes

If yes, what is the GPU card and driver?

NVIDIA GeForce GTX 1050 Ti

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

No response

@MStraeten
Copy link
Collaborator

did you also try it with a clean darktable-config directory?
e.g. by starting via commandline: <wherever your darktable binary is>darktable.exe --configdir <a temporary location>

@mprichards
Copy link
Author

Yes, running with new config location doesn't work either.

@TurboGit
Copy link
Member

Something corrupted on your side, this would have been already reported as a huge regression and quite visible. I have no idea about the possible issue though.

@mprichards
Copy link
Author

Indeed, I was expecting to see that someone else had already logged an issue.

I've just installed 5.0 to a new location and renamed the original config dir in AppData and still does the same thing. When reinstalling it still thought darktable was already installed - are there any additional locations that need to be cleaned?

@MStraeten
Copy link
Collaborator

then it's time to get log files: see https://www.darktable.org/about/faq/#faq-windows-bugs

@mprichards
Copy link
Author

mprichards commented Jan 10, 2025

darktable-log.txt
This is the log from running with -d common - launched and tried to apply a couple of presets.

Repeated with -d all:
darktable-log-alldebug.txt

Let me know if there's anything else that would help.

@mprichards
Copy link
Author

Also just tried with -d verbose as well, and it crashed on start:
darktable-log-alldebug-verbose.txt

@ghwaldo
Copy link

ghwaldo commented Jan 10, 2025

Same Problem here WIN 10 after Upgrade to 5.0.
I've renamed the old darktable folder under appdata, but still presets of the modules are not applied.

@ghwaldo
Copy link

ghwaldo commented Jan 10, 2025

No errors in any log-files

I can enable the module, for example, tone eq, but clicking on any preset does simply nothing.
I can use the module when i manually set values, but no preset is setting any values in

  • tone eq
  • colour balance
  • local contrast
  • contrast eq ...

@mprichards
Copy link
Author

Just browsing through some of the commits that might be related and was looking at 4676fec#diff-02bcf1785397fb026217b2580c2e764e9f3420ab5cf3d3e6d5e00342d810831eR2970

I don't know GTK, but it made me wonder if some of the events are mapped differently in Windows, so I tested using right-click. Presets are applied if I click the item using a right-click rather than a left-click!

@europlatus
Copy link

Just posting to say that I recently had this issue of not being able to apply presets. I'm on Windows 10 and running 5.0.0.
Restarting Darktable did not fix the issue, but restarting my PC did. I'm monitoring to see if I can reproduce it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

6 participants
@TurboGit @mprichards @MStraeten @ghwaldo @europlatus and others