Summary: | crash while trying to switch database sqlite -> mysql | ||
---|---|---|---|
Product: | [Applications] digikam | Reporter: | Francesco Riosa <vivo75+kde> |
Component: | Database-Migration | Assignee: | Digikam Developers <digikam-bugs-null> |
Status: | RESOLVED WORKSFORME | ||
Severity: | crash | CC: | caulier.gilles |
Priority: | NOR | ||
Version: | 2.0.0 | ||
Target Milestone: | --- | ||
Platform: | Compiled Sources | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | 2.0.0 | |
Sentry Crash Report: |
Description
Francesco Riosa
2011-06-27 21:33:31 UTC
seem not too digikam related, looking also at the possible duplicate list, also at the re-opening of digikam the database was correctly set to mysql digiKam 2.0.0 RC is out. Please check if crash is reproducible with this version. Thanks in advance Gilles Caulier I assume the crash is not reproducable, and occurred immediately while switching database engines? Then it can be a digikam problem - the timing is very suspicious - but the backtrace does not help, even more if the crash is not reproducable. Only valgrind may show invalid memory operations. I'm not able to reproduce it, if it will happen again I'll try a fix |