darktable-org / darktable-org/darktable

lost work (skeleton)

Open
#21,136 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

no-issue-activity
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

i was editing and it glitched and closed once thought it was a connection problem. Then was working for another 45 mins and it kicked me out of the darkroom section and sent me back to the lighttable all of my work was displayed as skull heads and it said there was no image there when i tried to open it again.

Steps to reproduce

it kicked me out of the darkroom section and sent me back to the lightable
tole me there was no image

Expected behavior

not have skulls as my work

Logfile | Screenshot | Screencast

No response

Commit

No response

Where did you obtain darktable from?

darktable.org / GitHub release

darktable version

5.4.1

What OS are you using?

Windows

What is the version of your OS?

XPS 15 9570

Describe your system

No response

Are you using OpenCL GPU in darktable?

No

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.

Research direction

Start by reproducing the reported transition from darkroom to lighttable on Windows with darktable 5.4.1, checking whether edited work appears as skulls or reports no image. Gather the missing logfile, screenshots, system details, and reproduction steps; done means identifying a reproducible failure or documenting the evidence needed to investigate it.

Written by the indexing model from the issue text.

Assessment

Tech stack
c
Domain
desktop
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.