unsupported file format error and crash on CR3 files on versions 4.8.1 and 5.0.0 of Darktable

Greetings! I’m having trouble with Darktable opening my CR3 files, generated from my EOS R and EOS R5 Mark II cameras. I use Ubuntu 24.10. When I was using Ubuntu 24.04, I was able to open the CR3 files from my EOS R camera in Darktable. After the upgrade to 24.10, it seems that I keep getting an ‘unsupported file format’ error on all my CR3 files (from both R and R5 mark II), and then Darktable crashes. So it seems I lost support on my EOS R files now as well.

I tried both the Ubuntu Darktable package (ver. 4.8.1), and also installed via the Darktable repo (ver. 5.0.0) but both Darktable versions give me the same error, followed by a program crash.

Does anyone have a similar experience or could point out what the issue could be? Right now I’m running Darktable via its official Docker container, and that way both 4.8.1 and 5.0.0 versions work and can open my CR3 files. But it’s an annoying way of doing things.

Thanks for your time!

I don’t think we have an official docker container.

I think you should start with posting the output from dt starting in terminal using the -d common flag. Ideally the 5.0 version

The EOS R5 Mark II is not yet supported by LibRaw, so that is normal, and can be taken out of testing here.

The EOS R is supported for a while, and should be working.

Also the output of darktable --version please.

Did you rebuild dt after the upgrade?

this is the docker image I use:
lscr.io/linuxserver/darktable:latest

All the debug output below comes from running Darktable 5.0.0, installed via the official repo

I’ve added
darktable_bt_45I5Z2.txt (82.4 KB)
the debug output I get from darktable, when doing a right click on the CR3 file I want to open.

I notice that Darktable 5.0.0 also crashes if I press the “add to library” button as the first thing I do when I start the application. I ran it in a terminal via the command:
darktable -d all > darktable_output

and attached the output
darktable_output.txt (547.1 KB)

Thanks for your time!

No, I didn’t build it from source. I used the Ubuntu version/package of Darktable that came with the upgrade from 24.04 to 24.10

Do you have LUA scripts?

2.7181 LUA ERROR : cannot open /home/potatoes666/.config/darktable/luarc: No such file or directory

What happens if you start dt using a clean config (as a test)? darktable --configdir "~/.config/darktable-test"

There is no “official” repo, so better state which binaries you got from where exactly. All Linux binaries (if not part of the distro itself, and Ubuntu ships only 4.8.1 as latest) are built and supported by the 3rd party repo maintainers and community volunteers, not by the dt project any “official” way.

I started Darktable with the command:
darktable -d all > darktable_output_when_add_to_library_is_clicked.txt

to capture the debug output when clicking the add to library button
darktable_output_when_add_to_library_is_clicked.txt (548.6 KB)

This is the debug output when I open a EOS R file with darktable, by doing a “right click → open with Darktable” on the file
darktable_bt_76AH02.txt (82.4 KB)

I tried to do the same action by running Darktable in a terminal, but drag-drop a CR3 file on Darktable doesn’t seem to have an effect, lighttable remains empty

Thanks for your time!

LibRaw -> ENABLED - Version 0.22.0-Devel202403

In any case, the LibRaw version used in your build should cover the EOS R just fine…

Hm, don’t remember installing any Lua scripts

Running the command
darktable --configdir “~/.config/darktable-test”
still causes the same behavior from Darktable: it crashes when pressing the “add to library” button, and doesn’t open an EOS R CR3 file when I drag-drop it

All crashes seem to come from pango, so this could be a library version problem specific to 24.10… Have you changed the dt theme and/or system fonts in any way?

Edit: note this comment:

I first disabled and them removed fonts-symbola (and other related packages). This has resolved the issue for me.

Not to my knowledge. The one thing I’ve done is use 10 bit color on my Xorg.conf file, but not sure if that has an effect (I can try to switch to 8 bit color as an experiment if you want)

Btw, I guess this could be coming from the new places icons/buttons introduced in the “add library” dialog in 5.0.0, so might be worth reporting on GitHub, maybe someone has a different idea for a workaround as it might hit on some other systems w/ this “buggy” pango version…

Have you tried with the official appimage?

Not sure what image that would be, if you have a link please do send it here

I used the docker images that are found here:
https://hub.docker.com/r/linuxserver/darktable

Wow, thanks a lot for this suggestion! I removed the fonts-symbola package and now I’m able to open EOS R CR3 files and also click the “add to library” button in Darktable 5.0.0

1 Like

Hm, no, didn’t install Darktable this way

I used the instructions/repo found here, for Ubuntu:
https://software.opensuse.org/download.html?project=graphics:darktable&package=darktable

However, it seems that the solution was to remove the fonts-symbola package. Doing that fixed the issues I was seeing so far

It would be nice to document this in a darktable github issue for others to discover if they have a similar issue.

1 Like