Start a new thread. Post the results from using darktable -d common and darktable-cltest
Does anybody have issues with Flatpak?
I am getting
ID Branch Op Remote Download
1. [✗] org.darktable.Darktable stable u flathub 1.0 kB / 34.6 MB
Error: While pulling app/org.darktable.Darktable/x86_64/stable from remote flathub: opcode close: Corrupted file object; checksum expected='662e30592e5ca61255bfd6c1304c293b66448631abcfadef87917145429be7f6' actual='f1685d2d5ad378c33b29bb75856c4d5a61d8abd47e88b498a87a9e48ebc70721'
Updates complete.
error: There were one or more errors
This fixed it
Run sudo flatpak repair or flatpak --user repair, fixed it for me
Thanks to
What an amazing way to kick off the holidays! Thank YOU for making it happen!
Thanks for this! While I will be spending first few days of Christmas visiting family, I have some vacation time after that to explore the new version properly. For now I’ve built it, processed a few older images playing with sigmoid and the primaries and initial impressions are nice.
This is a great software piece, done by some great people, and also a nice Christmas present.
Thank you. Merry Christmas to all.
Not sure if my following advice can help:
in preferences > processing > CPU/memory > darktable resources : try “small”. If this helps you may increase to “default” etc…
(I had crashes without any message when I was testing 4.5 6 weeks ago. I had this on a by myself redefined “unrestricted” since that worked under 4.4.2, but had to lower to “large”.)
Darktable is the best! It’s certainly top-notch and compares to commercial options and does a lot of stuff better. Thank you SO much to all the developers! You folks are great.
I hope this version will alleviate the system freeze i get when DT first starts, I think it’s due to OpenCL and Wayland.
Can’t wait to try it - still in testing repos for Arch.
Another advice can be found here:
Replying to myself, for whoever else need this OBS repository just updated today with 4.6.0 binaries: get them at Install package graphics:darktable / darktable
thanks!
Unfortunately your suggestioni doesn’t work,
See also my other suggestion as found by googling on the error code.
Well we don’t support Wayland yet, so…
Fair enough, but I want to see if the bug in OpenCL you fixed will help me as well. Because, once DT starts working, the system is fine. It almost exclusively happens the first time DT is started after boot.
On the unofficial note, any plans to start supporting Wayland?
Certainly, but Wayland is not feature complete for our needs.
Certainly, but Wayland is not feature complete for our needs.
Aside of color profiling, anything else that is major? Might be interesting to share with us so we could reconsider it as well or ask Wayland devs to include it.
Its the color management stack, mostly.
Hi Ivan, probably solution can be found on Github issue # 15686: Same error code but with dt 4.4.2.
There is a thread about the same error code and wording on Github issue # 15686.
He has a different issue (I think Lua). Please see this thread and let’s keep this one on topic.