On Mon, Nov 21, 2016 at 4:17 PM, Niccolò Belli <darkba...@linuxsystems.it> wrote: > On domenica 20 novembre 2016 19:24:06 CET, Tobias Ellinghaus wrote: >> >> I assume you filed a bug in our bug tracker, together with the backtrace? > > > I just switched to Darktable since a couple of days (ex Adobe Lightroom > user) and I just finished reading the user manual. I just had the time to > compile it from git to see if it still crashes (it does) and I'm still > trying to convince darktable to crash when I attach it do gdb. I will > probably keep using darktable attached to gdb if it works so well, > apparently. > >> That is not feasible as we rewrite the XMP files all the time. Not just >> when you edit the image in darkroom. > > > I was thinking about something like "when you start it, darktable detects if > a crash happened, or it simply checks if the database is consistent with the > XMP files" --> "if not, it immediately shows which photos are not > consistent, showing for each one the full history of both db and XMP, along > with a preview for both of them" --> "it asks for each photo where do you > want to get the metadata from, either from db or XMP. If you want to keep > the history from the XMP it updates the db entry, otherwise it overwrites > the XMP file" --> "restores the normal operating mode". It should be > definitely feasible.
please do collect a useful stack trace and then fixing the crash will be faster than doing any of this. -j. ____________________________________________________________________________ darktable user mailing list to unsubscribe send a mail to darktable-user+unsubscr...@lists.darktable.org
