Summary: | DIgikam crash when saving photo (by overwriting the original file) | ||
---|---|---|---|
Product: | [Applications] digikam | Reporter: | jcb1985 <jcbodez> |
Component: | Albums-Engine | Assignee: | Digikam Developers <digikam-bugs-null> |
Status: | RESOLVED FIXED | ||
Severity: | crash | CC: | caulier.gilles, jcbodez, marcel.wiesweg |
Priority: | NOR | ||
Version: | 1.0.0 | ||
Target Milestone: | --- | ||
Platform: | Ubuntu | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | 5.7.0 | |
Sentry Crash Report: | |||
Attachments: | New crash information added by DrKonqi |
Description
jcb1985
2010-01-11 14:15:46 UTC
Strange, in deep QCore crash. Could this be related to the malloc check stuff? Yes, certainly... Gilles (which doesn't understand why libc exception have been enabled in KDELibs...) Can you check if digikam still crashes if you 1. open a terminal 2. type "export MALLOC_CHECK_=0" + enter 3. type "digikam" + enter Or maybe "export MALLOC_CHECK_=" without the 0. I tried both export MALLOC_CHECK_=0 and export MALLOC_CHECK_= it crashed both times. note that sometimes the first picture modifications saving works, but it always crash with a second picture modifications saving But the backtrace you gave us is not from a crash while saving a picture. The crash you reported must have happened directly after starting digikam, probably even before you saw any window. Can you give us another backtrace when digikam crashes while saving an image? I can assure you that I can use digikam without a single crash for hours! It ONLY crashes when I edit a picture then save it. I'll give you a another backtrace in a few minutes Created attachment 39787 [details]
New crash information added by DrKonqi
the new backtrace you asked, occured when saving after editing a pic
Has anyone else got an idea what this could be? Looks completely strange. I would suspect a problem with your Qt installation. could it be related to Qt 4.6 ? digiKam has been compiled with it in this ppa. or because of KDE 4.4 RC1 ? KDirWatchPrivate::Entry::findSubEntry (this=0xe32530) at ../../kio/kio/kdirwatch_p.h:161 I would suggest a kdelibs (KDirWatch) bug. *** This bug has been marked as a duplicate of bug 222974 *** Since digiKam 5.0.0, KDirWatch was been replaced by QFileSytemWatcher. It will not reproducible. Gilles Caulier |