Summary: | Digikam crashes on start-up after throwing an instance of 'std::bad_alloc' | ||
---|---|---|---|
Product: | [Applications] digikam | Reporter: | Jeff Robinson <jeffnik> |
Component: | Thumbs-Engine | Assignee: | Digikam Developers <digikam-bugs-null> |
Status: | RESOLVED FIXED | ||
Severity: | crash | CC: | caulier.gilles |
Priority: | NOR | ||
Version: | 1.5.0 | ||
Target Milestone: | --- | ||
Platform: | Slackware | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | 6.3.0 | |
Sentry Crash Report: |
Description
Jeff Robinson
2010-11-03 01:43:58 UTC
*** This bug has been marked as a duplicate of bug 247977 *** Apparently my digikam4.db had become corrupt during the crash when searching for duplicates. I backed up the db file and deleted the original. Now Digikam 1.5 correctly starts and runs (though it did give me a warning my local had changed from ISO-8890-1 to ISO-8890-1). The only issue I have now is that if I continue with the new database all my RAW files have lost their tags/captions. At least Digikam works again and I have the labelled JPEGs in the same directories! Fixed with bug #247977 |