darktable-org / darktable-org/darktable

Renaming without file extension causes crash

Open
#21,684 12 comments 1 reaction 1 assignee View on GitHub

@anoderay is already working on this.

Since Aug 2, 2026.

Dominant language
C
Stars
13.1k
Forks
1.4k
Avg merge
22h 14m
Merged PRs (30d)
198

Description

Is there an existing issue for this?
  • I checked and did not find my issue in the already reported ones
Describe the bug

If you use the script "rename images" to give a file name without file extension can make Darktable unstartable

Steps to reproduce
  1. Rename a imagefile filename.extension (camper.ORF) to filename (camper) by using the script rename images
  2. Duplicate this image in lighttable - actions on selection - duplicate
  3. End Darktable
  4. Restart fails with error
  5. Delete last entry in library.db - images lets you start Darktable again
Image [DT restart.txt](https://github.com/user-attachments/files/30630381/DT.restart.txt) [DT start-duplicate-rename-close.txt](https://github.com/user-attachments/files/30630380/DT.start-duplicate-rename-close.txt) Image
Expected behavior

In this case the error shouldn't say "cannot write XMP..." but should name the reason for that

Logfile | Screenshot | Screencast

DT restart.txt
DT start-duplicate-rename-close.txt

Logfiles are the same as mentioned before. That's my first bug report, so please be patient with me

Commit

No response

Where did you obtain darktable from?

distro packaging

darktable version

5.6.0-1.1+117.1

What OS are you using?

Linux

What is the version of your OS?

Ununtu 24.04.4 LTS

Describe your system

Relevant: I made testing with .ORF and .jpg file extensions, tested different imagefiles in different directories. Alsways the same behaviour. See more here pixls.us

Are you using OpenCL GPU in darktable?

No response

If yes, what is the GPU card and driver?

No response

Please provide additional context if applicable. You can attach files too, but might need to rename to .txt or .zip

No response

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.