We’re proud to announce the new feature release of darktable, 4.0.1!
The github release is here: https://github.com/darktable-org/darktable/releases/tag/release-4.0.1.
As always, please don’t use the autogenerated tarball provided by github, but only our tar.xz file. The checksums are:
$ sha256sum darktable-4.0.1.tar.xz 5fef81e0c0079977a3cdc3627eed777280c2346d023c5d176c1f4a62cbe51d68 darktable-4.0.1.tar.xz $ sha256sum darktable-4.0.1.1_x86_64.dmg f4914a6c49a2e3a815c75b199d8da31a3160e179e8272e8fb1075ce48b188e65 darktable-4.0.1.1_x86_64.dmg $ sha256sum darktable-4.0.1.1_arm64.dmg 961af68e76fb274b0451bf287a9eb243f917ef68b933d48963534bfe328a955f darktable-4.0.1.1_arm64.dmg $ sha256sum darktable-4.0.1.exe 96b584edbc7d65f26b76dc7c57b9dce6fe33792b839f0ac4c712cd6834051dad darktable-4.0.1-win64.exe When updating from the stable 3.8.x series, please bear in mind that your edits will be preserved during this process, but the new library and configuration will no longer be usable with 3.
This is a companion discussion topic for the original entry at https://www.darktable.org/2022/09/darktable-4.0.1-released/
23 Likes
Merci
2 Likes
Very nice - yet again big kudos/thanks to all developers and supporting folks.
I am building the new version right now 
1 Like
I’ve tried to merge DNGs from my Android phone (a OnePlus 6T) before and they would always end up with a black output. This sounds like it would fix this issue, but it still results in black DNGs. How do I properly open a bug report with problematic DNGs attached?
You may have to share the DNG files via a link, and include that in the bug report.
1 Like
Thanks! I will open an issue tonight when I have more time to do a proper write-up.
And thanks to the amazing team behind DarkTable, this is already an amazing piece of software and it keeps getting better 
1 Like
There were no commits since June 4…
That’s why the section is empty…
Which is unfortunate, given all the good stuff there, ready to be merged…
Yeah well, this is what happens when a project is volunteer powered.
If you have the will and time to contribute to rawspeed maintenance, please do get in touch with Roman.
Hello! I have been looking for the print module for several days and I see that in this version it does not work.
In the keyboard shortcuts section it is still shown with the “P” key but when you press it it does not appear.
I’m looking for information on the forums and I didn’t find anything.
Can you give me some light on this? Thanks.
All the best.
@Subdes hi & welcome. I assume that you’re on windows, the print module is not available on that OS.
The print module has never been ported to Windows which is lacking contributors. If you are a dev or know a dev working on windows willing to help it would be nice We have said many time that we need more people working on Windows, there is no magic.
The alternative is very simple though, move to GNU/Linux and you’ll have the print module
3 Likes
I’m afraid the print module doesn’t work for me on any Linux distro.
On Windows I know it doesn’t work because the print module works with cups.
but since 4.0.1 it stopped working on Mint, Zorin, Arch and various distros I’ve tried.
I already saw where the error is. Installing the version of Snap Store does not work the printing module, but if you install it from Flathub it works.
It would be great if they developed something to work on Windows. I have several acquaintances who would appreciate it.
All the best!!
Then it means that the distro did not compile darktable with libcups installed. I know for sure the print module is working as I’m using it almost once a week. There is many optional dependencies for darktable, each one activating some specific support like the print module or the map view (need the libosmgpsmap), or support for external formats like AVIF, J2K, HEIF… So if you find some missing piece just report upstream, the darktable team cannot do something about this.
1 Like
which linux distribution are you on?