File import not working in darktable 4.8

On my Fedora 39 system, I just installed the darktable 4.8 RPM from the graphics_darktable RPM repo. It works for photos already in my database, but I can’t import new photos. Both add to library and copy & import show the directory tree, but do not show any files in those directories. I have unchecked select only new pictures and ignore non-raw images, with no change.

Has anyone else seen this? Is there a fix other than re-installing the program from a different source?

Anything wrong with the “official” RPM from the updates channel?

That RPM does the same thing – no files are shown in the directories.

Can you post a screenshot of your import GUI?

I figured out what’s going on. All my photos are Canon CR3 RAW files. When I open an old directory that contains CR2 files from my old camera, I see the files. Only the CR3 files are missing. This leads me to suspect that the binary file in the RPM was compiled without CR3 support.

Anyway, since you asked, here’s my import window:

Correct, exiv2 0.27.x in Fedora 40 and earlier does not support CR3, so nor does (“official” RPM of) darktable. This will change in Fedora 41, exiv2 0.28.x is currently being tested in Rawhide.

1 Like

Thanks. Now I’m reminded why I compiled darktable 4.6.1 from source with an updated exiv2. :upside_down_face:

Unless there’s a way to revert the database from 4.8 to 4.6, I’ll need to recompile 4.8 from source as well.

Since you are on F39, you can use OBS too.

https://software.opensuse.org/download.html?project=graphics:darktable&package=darktable

I think also the OBS one would need replacing the system exiv2 w/ the exiv2-non-suse one?

Yes the OBS uses the non system one. I’m on F40 and I can open cr3 files via OBS.

If you haven’t done too much work with 4.8 (you decide what’s “too much” :wink: ):
darktable saves a copy of the databases before updating to the newer scheme next to the new database (renamed to xxx.db-pre-<version>), so you could (with darktable not running), revert to those databases.
Sorry, I’m not sure what happens with the config files.

There’s also the official AppImage.

I believe fedora has opted not to build exiv2 with bmff support enabled because IBM/Red Hat is so risk adverse and they’re scared of infringing on a patent.

That is total nonsense and I hope I’m wrong about all of it.

Thanks for the tips. I installed 4.8 from the OBS package and everything is good. I can read CR3 files again.

Correct, exiv2 0.27.x in Fedora 40 and earlier does not support CR3, so nor does (“official” RPM of) darktable.

The previous “official RPMs” of darktable installed their own version of exiv2, with bmff support. For some reason, the one for Fedora 40 does not.

Check:
https://download.opensuse.org/repositories/graphics:/darktable/Fedora_39/x86_64/
https://download.opensuse.org/repositories/graphics:/darktable/Fedora_40/x86_64/

:worried:
What’s exactly the solution that’s working for other people?

I waited for darktable to become available on F40 before upgrading…

AppImage (official), flatpak, nixpkgs.

1 Like