| Summary: | darktable raw import fails | ||
|---|---|---|---|
| Product: | [Applications] digikam | Reporter: | Wren Falcon <wren-falcon> |
| Component: | Plugin-RawImport-Darktable | Assignee: | Digikam Developers <digikam-bugs-null> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | CC: | caulier.gilles |
| Priority: | NOR | ||
| Version First Reported In: | 9.0.0 | ||
| Target Milestone: | --- | ||
| Platform: | Arch Linux | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | 9.1.0 | |
| Sentry Crash Report: | |||
| Attachments: | excerpt of logs from digikam 9.1.0 pre-release when trying to import from darktable | ||
|
Description
Wren Falcon
2026-04-21 04:42:34 UTC
Get a debug trace following the instructions here : https://www.digikam.org/contribute/#freezes-and-other-run-time-issues Another way is to test current 9.1.0 pre-release using the AppImage bundle to see if the problem is reproducible : https://files.kde.org/digikam/ Gilles Caulier Created attachment 191672 [details]
excerpt of logs from digikam 9.1.0 pre-release when trying to import from darktable
(In reply to caulier.gilles from comment #1) > Get a debug trace following the instructions here : > > https://www.digikam.org/contribute/#freezes-and-other-run-time-issues > > Another way is to test current 9.1.0 pre-release using the AppImage bundle > to see if the problem is reproducible : > > https://files.kde.org/digikam/ > > Gilles Caulier Pre-release AppImage has same problem. See above logs. It appears (though it's not evident from the logs) that the temporary Darktable file is empty (0 bytes). From your log, the command line passed to DarkTable is this one :
DarkTable arguments: QList("--library", ":memory:", "--luacmd", "dofile('/tmp/LuaScript-TZBWnS-295978a0')", "--conf", "plugins/lighttable/export/icctype=-1", "--conf", "lua/export_on_exit/export_filename=/tmp/Darktable-QCXSQE-f6658561", "/run/media/wren/Crucial X9/Canon/IMPORT_5/2026-04-20/IMG_9310.CR3")
and it return OK but generated output file is empty or broken:
unknown: DarkTable :: return code: 0 :: Exit status: QProcess::NormalExit
unknown: Failed to read header of file "/tmp/Darktable-QCXSQE-f6658561"
unknown: Failed to read header of file "/tmp/Darktable-QCXSQE-f6658561"
unknown: Failed to read header of file "/tmp/Darktable-QCXSQE-f6658561"
unknown: Failed to read header of file "/tmp/Darktable-QCXSQE-f6658561"
unknown: Failed to read header of file "/tmp/Darktable-QCXSQE-f6658561"
unknown: Failed to read header of file "/tmp/Darktable-QCXSQE-f6658561"
Digikam::DImg::load: "/tmp/Darktable-QCXSQE-f6658561" : Unknown image format !!!
Q : can you share this CR3 file through a cloud storage:
/run/media/wren/Crucial X9/Canon/IMPORT_5/2026-04-20/IMG_9310.CR3
Actually... presumably the issue is with the darktable build. From digikam logs: > unknown: DarkTable arguments: QList("--library", ":memory:", "--luacmd", "dofile('/tmp/LuaScript-TZBWnS-295978a0')", "--conf", "plugins/lighttable/export/icctype=-1", "--conf", "lua/export_on_exit/export_filename=/tmp/Darktable-sEGYOv-0cdfce78", "/run/media/wren/Crucial X9/Canon/IMPORT_5/2026-04-20/IMG_9310.CR3") And darktable --version (indicates no Lua): > darktable 5.4.1 > Copyright (C) 2012-2026 Johannes Hanika and other contributors. > > Compile options: > Bit depth -> 64 bit > Exiv2 -> 0.28.7 > Lensfun -> 0.3.4 > Debug -> DISABLED > SSE2 optimizations -> ENABLED > OpenMP -> ENABLED > OpenCL -> ENABLED > Lua -> DISABLED > Colord -> ENABLED > gPhoto2 -> ENABLED > OSMGpsMap -> ENABLED - map view is available > GMIC -> ENABLED - Compressed LUTs are supported > GraphicsMagick -> ENABLED > ImageMagick -> DISABLED > libavif -> ENABLED > libheif -> ENABLED > libjxl -> ENABLED > LibRaw -> ENABLED - Version 0.22.0-Release > OpenJPEG -> ENABLED > OpenEXR -> ENABLED > WebP -> ENABLED I'll get a darktable build with Lua enabled and test it with that. Right. LUA is used by digiKam to pass all the settings to DarkTable. Swapped out darktable-2:5.4.1-2 from the official Arch Linux repos for darktable-git (darktable-git-5.5.0.r1007.gd697177169-1) from the AUR, which is configured to build Lua support in, and it resolved my issue both on digiKam 9.0.0 and the 9.1.0 pre-release AppImage. digiKam is able to load the edited image into the image editor window. Would you still be needing that .CR3? Git commit cf823b072131a9391cdee2058dea2790158f7eb6 by Gilles Caulier. Committed on 21/04/2026 at 05:53. Pushed by cgilles into branch 'master'. Add note about the requirement of LUA support in Darktable. M +4 -0 setup_application/editor_settings.rst https://invent.kde.org/documentation/digikam-doc/-/commit/cf823b072131a9391cdee2058dea2790158f7eb6 No not need the CR3 as the problem is fixed now. |