ldd /usr/bin/darktable | grep -i libicu
libicui18n.so.72 => not found
libicuuc.so.72 => not found
libicuuc.so.73 => /usr/lib/libicuuc.so.73 (0x00007ff1e9800000)
libicudata.so.73 => /usr/lib/libicudata.so.73 (0x00007ff1dc200000)
Raj, why not compile darktable yourself?
Can I delete the chaotic-arch DT and install it from aur? Will it solve the problem?
@Claes can you tell me the process if I find it comfortable (confident in following the instructions) I’ll give it a try.
Comfortable or not – I just PM’d it to you.
Here’s my build script, which I have posted several times. You’ll need to come darktable first, and install the build dependencies listed in the README file.
Thanks! 
@Claes build my first Darktable with your endeavour.txt
/opt/darktable/bin/darktable --version
this is darktable 4.5.0+38~g57f0f67816
copyright (c) 2009-2023 johannes hanika
https://github.com/darktable-org/darktable/issues/new/choose
compile options:
bit depth is 64 bit
normal build
SSE2 optimized codepath enabled
OpenMP support enabled
OpenCL support enabled
Lua support enabled, API version 9.1.0
Colord support enabled
gPhoto2 support enabled
GraphicsMagick support enabled
ImageMagick support disabled
libavif support enabled
libheif support enabled
libjxl support enabled
OpenJPEG support enabled
OpenEXR support enabled
WebP support enabled
/opt/darktable/bin/darktable-cmstest
darktable-cmstest version 4.5.0+38~g57f0f67816
this executable was built with colord support enabled
darktable itself was built with colord support enabled
primary CRTC is at CRTC 0
DP-4 the X atom and colord returned different profiles
X atom: _ICC_PROFILE (0 bytes)
description: (none)
colord: "/home/raj/.local/share/icc/edid-44da77e788024f87c9ac2a6e19671453.icc"
description: Dell Inc. 24"
Better check your system setup
- some monitors reported different profiles
You may experience inconsistent color rendition between color managed applications
What is this?
/opt/darktable/bin/darktable-cltest
0.0818 [dt_get_sysresource_level] switched to 1 as `default'
0.0818 total mem: 15854MB
0.0818 mipmap cache: 1981MB
0.0818 available mem: 7927MB
0.0818 singlebuff: 123MB
0.0818 OpenCL tune mem: OFF
0.0818 OpenCL pinned: OFF
[opencl_init] opencl related configuration options:
[opencl_init] opencl: ON
[opencl_init] opencl_scheduling_profile: 'very fast GPU'
[opencl_init] opencl_library: 'default path'
[opencl_init] opencl_device_priority: '!0,*/!0,*/!0,*/!0,*/!0,*'
[opencl_init] opencl_mandatory_timeout: 200
[opencl_init] opencl library 'libOpenCL' found on your system and loaded
[opencl_init] found 1 platform
[opencl_init] found 1 device
[dt_opencl_device_init]
DEVICE: 0: 'Ellesmere'
PLATFORM NAME & VENDOR: AMD Accelerated Parallel Processing, Advanced Micro Devices, Inc.
CANONICAL NAME: amdacceleratedparallelprocessingellesmere
DRIVER VERSION: 3224.4
DEVICE VERSION: OpenCL 1.2 AMD-APP (3224.4)
DEVICE_TYPE: GPU
GLOBAL MEM SIZE: 7957 MB
MAX MEM ALLOC: 6763 MB
MAX IMAGE SIZE: 16384 x 16384
MAX WORK GROUP SIZE: 256
MAX WORK ITEM DIMENSIONS: 3
MAX WORK ITEM SIZES: [ 1024 1024 1024 ]
ASYNC PIXELPIPE: NO
PINNED MEMORY TRANSFER: NO
MEMORY TUNING: NO
FORCED HEADROOM: 400
AVOID ATOMICS: NO
MICRO NAP: 250
ROUNDUP WIDTH: 16
ROUNDUP HEIGHT: 16
CHECK EVENT HANDLES: 128
PERFORMANCE: 2.594
TILING ADVANTAGE: 0.000
DEFAULT DEVICE: NO
KERNEL BUILD DIRECTORY: /opt/darktable/share/darktable/kernels
KERNEL DIRECTORY: /home/raj/.cache/darktable/cached_v1_kernels_for_AMDAcceleratedParallelProcessingEllesmere_32244
CL COMPILER OPTION: -cl-fast-relaxed-math
KERNEL LOADING TIME: 4.8694 sec
[opencl_init] OpenCL successfully initialized. Internal numbers and names of available devices:
[opencl_init] 0 'AMD Accelerated Parallel Processing Ellesmere'
[opencl_init] FINALLY: opencl is AVAILABLE and ENABLED.
[dt_opencl_update_priorities] these are your device priorities:
[dt_opencl_update_priorities] image preview export thumbs preview2
[dt_opencl_update_priorities] 0 0 0 0 0
[dt_opencl_update_priorities] show if opencl use is mandatory for a given pixelpipe:
[dt_opencl_update_priorities] image preview export thumbs preview2
[dt_opencl_update_priorities] 1 1 1 1 1
[opencl_synchronization_timeout] synchronization timeout set to 0
[dt_opencl_update_priorities] these are your device priorities:
[dt_opencl_update_priorities] image preview export thumbs preview2
[dt_opencl_update_priorities] 0 0 0 0 0
[dt_opencl_update_priorities] show if opencl use is mandatory for a given pixelpipe:
[dt_opencl_update_priorities] image preview export thumbs preview2
[dt_opencl_update_priorities] 1 1 1 1 1
[opencl_synchronization_timeout] synchronization timeout set to 0
Now how to check when a new version is available and how to build it?
Again Thanks “for making me go where I have not gone before”
Good, Raj!
Now how to check when a new version is available and how to build it?
Ho-hum: See lines 33-36 in the document I sent you.
I am unable to pin DT as there is no option to do so. It is also not shown in “Show Apps” (list of installed apps)
Ho-hum: See lines 30-31 in the document I sent you.
DT starts it is shown in the launch pad but there is no option to pin it. Can you please explain what is a task manager.
Are you using Endeavouros?
When you have started dt, an icon will show up at the bottom of your monitor. In my case it is the 3rd icon from the right.
Right-click on that icon and select “pin to task manager”
As mentioned there is no such option and I am using Garuda Gnome. The icon is there in the Dock
Then you will have to consult Garuda manuals.
My info was based on using endeavouros.
Ok
Solved by installing DT in /usr/ and not in /opt/Darktable/
If the question is related to the colour management warning, it means that there are different profiles reported by the two sources darktable can use. The x-atom source is not set; colord is set to some automatically generated (EDID) profile, I think.
There’s an old thread here:
There’s a setting in darktable’s preferences governing where the display profile is obtained from. The choices are x-atom, colord or both.
I assume you are not working with a profiled display. Maybe you should set that config option to colord, I assume the automatic profile is better than nothing. I could be wrong, of course.
I had calibrated my monitor on the mac side and have a calibrated profile which I have loaded (on Garuda linux settings )and also put it in .config-darktable-color-out.
So how to point to it?
I really don’t think you need it in the color-out directory (that’s for exports).
Given that Garuda is based on Arch:
https://wiki.archlinux.org/title/ICC_profiles#Loading_ICC_profiles