Skip to content

database: name library.db in its corruption dialog - #22497

Open
da-phil wants to merge 1 commit into
darktable-org:masterfrom
da-phil:pl/fix_wrong_db_name_reference_in_gui
Open

da-phil wants to merge 1 commit into
darktable-org:masterfrom
da-phil:pl/fix_wrong_db_name_reference_in_gui

Conversation

@da-phil

@da-phil da-phil commented Oct 3, 2026 •

Copy link
Copy Markdown
Contributor

Summary

The library.db corruption dialog was copied from the data.db one and still printed dbfilename_data, so a broken library.db was reported as "data.db" while the terminal message named it "library.db".
The dialog's "delete database" button unlinks library.db, so a user trusting the dialog could delete the library believing they were removing data.db.

Checklist

  • I have read CONTRIBUTING.md and the coding style.
  • I have not merged master into the topic branch.
  • The pull request is one logical change, and every commit compiles on its own.
  • I ran the relevant tests: unit tests, src/tests/integration/ where the pixelpipe is touched, or darktable-cli as a headless smoke test.
  • New user-visible strings use _(), new preferences are registered in data/darktableconfig.xml.in.
  • A RELEASE_NOTES.md entry was added (only needed if fixing an issue in a release). Do not reference GitHub issues.

The library.db corruption dialog was copied from the data.db one
and still printed dbfilename_data, so a broken library.db was reported
as data.db while the terminal message named library.db.
The dialog's "delete database" button unlinks library.db,
so a user trusting the dialog could delete the library believing they were removing data.db.
@da-phil
da-phil force-pushed the pl/fix_wrong_db_name_reference_in_gui branch from cdac6e2 to abbefbf Compare October 3, 2026 11:54
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant