Is there an existing issue for this?
Describe the bug
Using darktable 5.4.1 on Windows. I have a particularly pesky edit with lots of steps, and I was careful to maintain my editing history snapshots so I can compare and revert various stages. After I closed and later reopened darktable, all the snapshots are gone.
Steps to reproduce
This happened in one particular instance. I am not using modules other than normal, but some modules - like color balance rgb - have multiple instances (8 in this case). Additionally, I have ~180 drawn mask shapes used across these modules. I do not know if this is or is not related to the occurence of the bug, but the only thing I can think of that makes this edit unique. Otherwise, the steps to reproduce are simple enough:
- edit an image in darkroom
- make a snapshot, observe that it is added to the snapshot list
- close darktable
- open darktable
- observe the snapshot is not in the snapshot list
Expected behavior
No response
Logfile | Screenshot | Screencast
No response
Commit
No response
Where did you obtain darktable from?
darktable.org / GitHub release
darktable version
5.4.1 from darktable.org
What OS are you using?
Windows
What is the version of your OS?
Windows 11 Pro
Describe your system
No response
Are you using OpenCL GPU in darktable?
None
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
The steps are reproducible with fresh edit history, after completely resetting the history stack.
I hope this is enough information to consider the bug report.
Is there an existing issue for this?
Describe the bug
Using darktable 5.4.1 on Windows. I have a particularly pesky edit with lots of steps, and I was careful to maintain my editing history snapshots so I can compare and revert various stages. After I closed and later reopened darktable, all the snapshots are gone.
Steps to reproduce
This happened in one particular instance. I am not using modules other than normal, but some modules - like color balance rgb - have multiple instances (8 in this case). Additionally, I have ~180 drawn mask shapes used across these modules. I do not know if this is or is not related to the occurence of the bug, but the only thing I can think of that makes this edit unique. Otherwise, the steps to reproduce are simple enough:
Expected behavior
No response
Logfile | Screenshot | Screencast
No response
Commit
No response
Where did you obtain darktable from?
darktable.org / GitHub release
darktable version
5.4.1 from darktable.org
What OS are you using?
Windows
What is the version of your OS?
Windows 11 Pro
Describe your system
No response
Are you using OpenCL GPU in darktable?
None
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
The steps are reproducible with fresh edit history, after completely resetting the history stack.
I hope this is enough information to consider the bug report.