-
Notifications
You must be signed in to change notification settings - Fork 1.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Darktable crash resulted in corrupted library #18158
Comments
Sounds like a similar problem as #18069. Can you try if reimporting of one image helps? |
Thanks for the reply! Before seeing it, I'd tried (separately) restoring snapshots of
Yes it did, after this the whole library now appeared. I'll see if the original issue is reproducible now. |
Yep, reproduced.
stack trace etc.
|
cmd+z issue see #18110 |
Describe the bug
Running with DarkTable 5.0.0 on MacOS 15.2, via homebrew.
I was editing a photo - had just applied a preset under the tone curve, then pressed
Cmd-Z
to undo it. The darktable process terminated. Upon reloading, the collection browser shows the expected list of collections, with the correct numbers of photos in parentheses, however double clicking any collection results in "there are no images in this collection" on the lighttable.The original photos and XMP files still seem to exist on disk, so I am guessing that only an index is corrupted.
Steps to reproduce
<<Will edit to populate reproduction and other details if I can reproduce, but first I need to figure out how to recover my library!>>
Expected behavior
No response
Logfile | Screenshot | Screencast
No response
Commit
No response
Where did you obtain darktable from?
distro packaging
darktable version
darktable 5.0.0
What OS are you using?
Mac
What is the version of your OS?
15.2
Describe your system?
No response
Are you using OpenCL GPU in darktable?
Yes
If yes, what is the GPU card and driver?
Apple M2
Please provide additional context if applicable. You can attach files too, but might need to rename to .txt or .zip
No response
The text was updated successfully, but these errors were encountered: