Version: 1.4.0 (using KDE 4.5.2) OS: Linux when building _al_ new fingerprints, DK crashed at some pomt - at avout 18% of 79246 pics. starting "suchen" at "build fingerprint", it just treats some dozens pics and crashes at one specific NIKON rws-pic . in both cases, bug-report assistence starts up, requires debug-data to be installed and assumes "useless bug report". the debug files _were_ installed before. Reproducible: Always Steps to Reproduce: just do it ;-) ! Actual Results: see above Expected Results: at least "debugging" should work without any problems.
Try digiKam 1.5.0. I fixed a crash in the same condition... Anyway, please post here a GDB backtrace of crash Gilles Caulier
? what is a "GDB" backtrace? ! as I wrote, I end up in an endless sequence of 1. crash 2. attempt to place a bugreport 3. get a statement, bug report was useless 4. get a statement, please install debug files 5. install again the debug-files (which were installed before!!) 6. without changes. 7. after re-starting DK exactly the same situation. --> "1."! I do not see DK 1.5 in my repositories, so I can`t install it. Right?! ! I have the mentioned file but the bug-reporting system doesn't allow for size. Rem.: As much as I know, pic sizes become larger and larger from the very beginning of digicams til today. So I suggest to support large files up to 20 .. 30 MB (standard pic sizes nowadays!!) ---------------------------------------------------------------------------- Am 17.10.2010 20:10, schrieb Gilles Caulier: > https://bugs.kde.org/show_bug.cgi?id=254483 > > > Gilles Caulier <caulier.gilles@gmail.com> changed: > > What |Removed |Added > ---------------------------------------------------------------------------- > CC| |caulier.gilles@gmail.com > > > > > --- Comment #1 from Gilles Caulier <caulier gilles gmail com> 2010-10-17 20:10:08 --- > Try digiKam 1.5.0. I fixed a crash in the same condition... > > Anyway, please post here a GDB backtrace of crash > > Gilles Caulier >
Read here : http://www.digikam.org/drupal/contrib Gilles Caulier
New digiKam 4.11.0 is available. https://www.digikam.org/node/740 Can you reproduce the problem with this release ?
With digiKam 5.0.0, this problem is not reproducible. I close this file now. Don't hesitate to re-open if necessary. Gilles Caulier