| Summary: | DK 2.0 beta 4 - crash when starting sw conversion | ||
|---|---|---|---|
| Product: | [Applications] digikam | Reporter: | Axel Krebs <axel.krebs> |
| Component: | Plugin-Editor-BlackWhite | Assignee: | Digikam Developers <digikam-bugs-null> |
| Status: | RESOLVED FIXED | ||
| Severity: | crash | CC: | caulier.gilles |
| Priority: | NOR | ||
| Version: | 2.0.0 | ||
| Target Milestone: | --- | ||
| Platform: | Ubuntu | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | 2.0.0 | |
| Sentry Crash Report: | |||
|
Description
Axel Krebs
2011-03-18 14:37:04 UTC
In KCrash Handler trace, there is no digiKam source code annoted. Please, try again to have a better backtrace... Gilles Caulier (In reply to comment #1) > In KCrash Handler trace, there is no digiKam source code annoted. > > Please, try again to have a better backtrace... > > Gilles Caulier digiKam is 2.0.0-beta4, component information is digiKam version 2.0.0-beta4 Exiv2 kann in JP2 speichern: Ja Exiv2 kann in JPEG speichern: Ja Exiv2 kann in PGF speichern: Ja Exiv2 kann in PNG speichern: Ja Exiv2 kann in TIFF speichern: Ja Exiv2 unterstützt XMP-Metadaten: Ja LibCImg: 130 LibClapack: internal library LibExiv2: 0.21.1 LibJPEG: 62 LibJasper: 1.900.1 LibKDE: 4.6.1 (4.6.1) LibKExiv2: 2.0.0 LibKMap: 2.0.0 LibKdcraw: 2.0.0 LibLCMS: 118 LibPGF: 6.09.44 - internal library LibPNG: 1.2.44 LibQt: 4.7.0 LibRaw: 0.13.1 LibTIFF: LIBTIFF, Version 3.9.4 Copyright (c) 1988-1996 Sam Leffler Copyright (c) 1991-1996 Silicon Graphics, Inc. Marble Widget: 0.11.0 (Stable Release) Parallelisiertes Entfernen von Mosaikmustern: Ja Datenbanktreiber: QSQLITE LibGphoto2: 2.4.10.1 LibKface: 2.0.0 LibKipi: 1.2.0 LibOpenCV: 2.1.0 Libface: 0.1 I hope, _not_ to experience further crashes ;-) ! -------------------------------------------------------------------------------- >> >> One thing comes into my mind: >> when trying to store a pics new version, and _before_ another action has >> completed, DK crashes. >> >> Idee: force waiting to end, including emptying potential internal caches(??) >> and waiting for finishing writing of files. >> Can you reproduce the crash with a difference backtrace ? Gilles Caulier Gilles: this will take some time. I get back to this topic Axel (In reply to comment #3) > Can you reproduce the crash with a difference backtrace ? > > Gilles Caulier I tested extensively with the pic, I experienced problems earlier (38 MB), and other pics with 15 and 107 MB: Variations: black-and-white, filmtype, lens filter, color type ( .. ), and their permutations. I further tried to provoke crashes: sharpening, denoising, size changes even "impossible" combinations! Since my bug was reported, my system (and therefore to above mentioned components!) might have changed, too: ! 2.6.35-28-generic-pae = DK Version 2.0.0-beta4 ! KDE 4.6.2 (4.6.2) I could not produce a new backtrace, as I had no crash. Assumption: more stable working KDE? --- "in brackets" --- There might be other gaps and suggestions: - how to store _one_ pic-version in _two_ file-types? - batch manager, might crash without explicite selection if storage path - batch-manager: how to store _several_ work sequences under different names to re-use as predefined "workflows"? These thoughts are quite preliminary at the moment, sorry! digiKam 2.0.0 RC is out. Please check if crash is reproducible with this version. Thanks in advance Gilles Caulier Checked several original-pics: jpg, size, HUGIN-mounted panorama. Cannot
find problems. You may want to close this bug.
Axel
Am 02.07.2011 12:02, schrieb Gilles Caulier:
> https://bugs.kde.org/show_bug.cgi?id=268817
>
>
>
>
>
> --- Comment #6 from Gilles Caulier <caulier gilles gmail com> 2011-07-02 10:02:10 ---
> digiKam 2.0.0 RC is out. Please check if crash is reproducible with this
> version.
>
> Thanks in advance
>
> Gilles Caulier
>
|