Summary: | Digikam crashes trying to save tool changes | ||
---|---|---|---|
Product: | [Applications] digikam | Reporter: | David Vincent-Jones <davidvj> |
Component: | Plugin-Editor-Sharpen | Assignee: | Digikam Developers <digikam-bugs-null> |
Status: | RESOLVED FIXED | ||
Severity: | crash | CC: | caulier.gilles |
Priority: | NOR | ||
Version: | 1.2.0 | ||
Target Milestone: | --- | ||
Platform: | Ubuntu | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | 1.7.0 | |
Sentry Crash Report: |
Description
David Vincent-Jones
2010-07-09 00:48:14 UTC
I cannot see any code from digiKam in thread where crash is located. Please give me another backtrace Also try digiKam 1.3.0 I use refocus filter there, a lots of time without any problem (Mandriva 2010.1) Gilles Caulier Gilles;
Yes I agree that I should move over to 1.3.0 but I have already tried to
do this also with the massive KDE additions and was unable to solve the
database problems. As a result I needed to totally 'flush' my system to
remove the extra materials and rebuild everything. I am reluctant to go
through this process again until there is a reliable and published deb
file with which to work.
Possibly part of my problem is that I use Gnome and there may have been
a problem in the ppa for KDE. If you tell me that DK runs better if I
use KDE then I will immediately change to KDE because DK is probably the
most important tool that I have on my system.
Now, the problem with the sharpening tool (on 1.2.0) appears to have
been quite consistent. After processing 3 or 4 images I find that
sharpening either does not start at all or it hangs and fails to
complete. It almost looks like a memory blockage problem. Although most
of this version shows remarkable advances, unfortunately this version
has proved, on my system, to be 'fragile' and frustrating with the
number of crashes that I am encountering.
I hope that at some point 1.3.0 is formally added into the Ubuntu
package manager. It is a wonderful program for which I heartily thank
you.
David
On Fri, 2010-07-09 at 07:32 +0200, Gilles Caulier wrote:
> https://bugs.kde.org/show_bug.cgi?id=243988
>
>
> Gilles Caulier <caulier.gilles@gmail.com> changed:
>
> What |Removed |Added
> ----------------------------------------------------------------------------
> Component|general |Sharpen
> Product|digikam |digikamimageplugins
>
>
>
>
#12 0x074b555b in __cxa_rethrow () from /usr/lib/libstdc++.so.6 #13 0x03fc075a in QMetaObject::activate (sender=0xee67780, m=0x70cc8c4, local_signal_index=2, argv=0xbfd2ce38) at kernel/qobject.cpp:3303 Looks like an exception thrown somewhere, caught by Qt and then rethrown. To find out the origin, you need to run under gdb, "catch throw", provoke the crash, and then get the backtrace. David, What's news in this file ? Can you test using digiKam 1.4.0 ? Gilles Caulier digiKam 1.6.0 is out: http://www.digikam.org/drupal/node/550 Please update and check if this entry still valid. Thanks in advance Gilles Caulier Later version has now resolved this issue |