Summary: | Crash during tagging | ||
---|---|---|---|
Product: | [Applications] digikam | Reporter: | Gareth <gareth.glaccum> |
Component: | Database-Albums | Assignee: | Digikam Developers <digikam-bugs-null> |
Status: | RESOLVED FIXED | ||
Severity: | crash | CC: | caulier.gilles, marcel.wiesweg |
Priority: | NOR | ||
Version: | 2.0.0 | ||
Target Milestone: | --- | ||
Platform: | Fedora RPMs | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | 7.0.0 | |
Sentry Crash Report: |
Description
Gareth
2011-06-15 08:19:43 UTC
Sound like a crash in database. Can you reproduce another backtrace ? Gilles Caulier I'll give it a shot (think I managed to reproduce the same bug this morning). However, my system may not have enough disk space to add all of the additional debuginfo packages required for a full trace (was 597MB compressed). Suspect it is the QT debug info that is the most use? (and the largest package :( ) I suspect this is always the same sort of memory corruption as with 262596 & friends. The backtraces differ slightly, but it's always about accessing a list of QVariants which is somehow invalid. *** This bug has been marked as a duplicate of bug 275688 *** Not reproducible using digiKam 7.0.0 beta1. |