GIMP no longer will open raw files

[FoutsSA]

Describe the bug

I installed darktable 4.6 from 4.4.2 and now after I edit a picture in darktable and close it gimp ver 2.10.36 complains there is now program to open raw file. I am running windows 10 ver.22H2 build 19045.3930

Steps to reproduce

1 update darktable from 4.* to 4.6
2 Open and edit raw file in updated darktable
3 Close the file and gimp will open but complains no program is installed to open raw files.

Expected behavior

darktable should open the raw file in my case NEF files and when closed gimp should open.

Logfile | Screenshot | Screencast

Opening 'C:\Users\SAFouts\Pictures\Nikon Transfer 2\124_DSC6405.NEF' failed: There is no RAW loader installed to open 'Raw Nikon' files.

GIMP currently supports these RAW loaders:

• darktable (http://www.darktable.org/), at least 1.7
• RawTherapee (http://rawtherapee.com/), at least 5.2

Please install one of them in order to load RAW files.

Commit

No response

Where did you obtain darktable from?

downloaded from www.darktable.org

darktable version

4.6.0

What OS are you using?

Windows

What is the version of your OS?

windows 10 ver.22H2 build 19045.3930

Describe your system?

32 gigs of RAM

Are you using OpenCL GPU in darktable?

Yes

If yes, what is the GPU card and driver?

4095MB NVIDIA GeForce GTX 1070 (MSI) ver 31.0.15.4633

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

This only started with darktable 4.6

[gi-man]

Duplicate of #15968

Will be fixed when we merge PR #15973

[victoryforce]

@FoutsSA Since this is a duplicate, I'm closing it. If you are interested in tracking the resolution process, you can subscribe to the issue mentioned above. One way or another, this problem should be fixed in release 4.6.1.

[FoutsSA]

Thanks much for letting me know, appreciate you guys. Steve

…

On Fri, Jan 26, 2024 at 10:51 PM Victor Forsiuk ***@***.***> wrote: @FoutsSA <https://github.com/FoutsSA> Since this is a duplicate, I'm closing it. If you are interested in tracking the resolution process, you can subscribe to the issue mentioned above. One way or another, this problem should be fixed in release 4.6.1. — Reply to this email directly, view it on GitHub <#16186 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BFTUD6XFPJ6S3SHPQCQMDGDYQSPWPAVCNFSM6AAAAABCLLHY7WVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSMJTGAZTSOJVGQ> . You are receiving this because you were mentioned.Message ID: ***@***.***>