That probably means the file isn’t marked as an executable, so the program used to handle the file type is opened. I know you’ve now solved this by installing from OBS, but for future reference:
In whatever file manager you use, you should make sure the file is marked executable. For example:
Once you do that, a double-click will run the application.
Galaxy Quest 
Such a great movie
Just noticed your reply…
It looks like you’ve built DT so are sorted. However, appimages are useful and worth bearing in mind, they don’t need building for a start. To use, set the downloaded .Appimage file to executable as above, and put it in some folder, I’m using Desktop. Then in Terminal type
./Desktop/X.AppImage
where X is the name of the appimage. DT should launch.
You can keep a selection of appimages to play with if you want, you just choose which you want when starting in Terminal. This is subject to the usual position that you can’t go backwards across a major release (unless you zap the database and associated files).
Thanks a lot. That’s a handy explanation. Bookmarking it!
If you don’t need the terminal (e.g. for debug logs), you can simply double-click the AppImage. Any required parameters (config directory etc.) can be set if you create a launcher icon - check the docs of your desktop environment.
Thanks kofa
Is there any way for an updated install to make the Sigmoid module the default tone-mapper instead of filmic rgb? I find it produces more accurate results.
In the settings under the processing section.
auto-apply pixel workflow defaults: select “scene-referred (sigmoid)”
Appreciate it!
Hi
I noticed slowness on my macMini M1 16GB. Every change in parameters for modules during processing photo was taking few seconds
After research I added opencl_force_c_locale=anything to darktablerc file
And this improved.
That points to a problem with your opencl drivers. Would you be able to check if you have the latest installed? If not, could you update them and check if having a opencl_force_c_locale= line in darktablerc still makes a difference? If with the latest drivers there is a difference, would you be able to report this issue on github, including the output of darktable-cltest? There will be a better chance there that somebody notices and picks it up so that for others with a similar configuration it won’t be a problem out of the box.
If you use dt in English, having the opencl_force_c_locale flag should not cause any issues.
Still no plans to have .deb for Ubuntu 22.04?
Same answer as before: use the appimage or flatpak. Older LTS distros are often hard to build for and don’t have new enough libraries.
4 posts were split to a new topic: Cinnamon desktop color shift
