Version: 0.10.0 (using KDE 4.2.4) OS: Linux Installed from: Ubuntu Packages Having discovered Digikam's excellent RAW-handling capabilities, I've been using it intensively over the past couple of days re-editing my collection of original files. Unfortunately I'm being plagued by crashes at random times. Worse still, the crashes take out my entire computer, leaving me with no alternative but to reset it and reboot. I can't even SSH into the system to attempt a fix, though the network card DOES respond to ping requests. In case this was a problem with faulty memory, I left memtest running overnight (more than 12 hours) and this found no problems at all. The two common points at which this is occuring is during the RAW import process (I'm using the RAW import tool) a couple of seconds after clicking the "import" button, and when using the free-rotation tool. But I can't find a pattern explaining what else triggers the crash; sometimes I can process a dozen pictures and then it will crash. But then I can re-import the same file with no problem. I've installed Ubuntu's debug version of Digikam and tried running it with gdb, but I'm not seeing any useful information at the time of the crash; possibly because the computer's hanging before it can print what gdb WOULD have told me? I've also tried running Digikam with strace in the hope that this might provide useful information, but I find that once the GUI has initialised, it seems to detach itself from strace so I don't see any further information. The result of the failure to get any useful debugging information means I'm not giving you enough to fix the bug, so this is as much a plea for ideas of how I might get more information about the crash; for example if it's possible to prevent Digikam from detaching from strace. ...of course, how much information I'll be able to get will be limited by the fact that there's no point in trying to write debugging information to a log as the crash will prevent that from being written to disc so I can see it after resetting the computer. But if I can capture as much as is still visible in a terminal it MIGHT be useful.
A cannont confirm that. i'm work everyday with RAW (MRW) and it work perflectly. As develpper, i use last version from svn of course, but there is no major changes in RAW interface from digiKam since 0.10.0. I suspect something wrong outside, perhaps database when data are recorded. Crash can be investiguated if you provide backtrace. Definitively, digiKam can never freeze your computer (especially when RAW file are decoded). This is relevant of a dysfunction from your computer or a bad low level driver. Anyway, we need more info : - Which Raw format ? - Which sofware version ? Go to Help/Components info for details? - Which operations exactly freeze digiKam ? - Install digiKam debug package and run it from the console. What can you see just before the freeze ? Gilles Caulier
Hi Gilles, I was surprised at the complete system crash as well - that's why I ran memtest in case there was a problem with memory. I'm seriously impressed with the way Digikam deals with RAW files - so much so I spent most of yesterday re-importing files I'd previously processed with Raw Therapee, even though I knew I'd get crashes along the way. Raw format: dcraw -i reports "Panasonic DMC-FZ8". I'm not sure if there's any more information I can get from this? Software version: digiKam version 0.10.0 Exiv2 can write to Jp2: Yes Exiv2 can write to Jpeg: Yes Exiv2 can write to Png: Yes Exiv2 can write to Tiff: Yes Exiv2 support XMP metadata: Yes LibCImg: 130 LibExiv2: 0.18 LibJPEG: 62 LibJasper: 1.900.1 LibKDE: 4.2.4 (KDE 4.2.4) LibKExiv2: 0.5.0 LibKdcraw: 0.4.2 LibLCMS: 118 LibPNG: 1.2.27 LibQt: 4.5.0 LibRaw: 0.6.15-Release LibTIFF: LIBTIFF, Version 3.8.2 Copyright (c) 1988-1996 Sam Leffler Copyright (c) 1991-1996 Silicon Graphics, Inc. Marble widget: 0.7.1 LibGphoto2: 2.4.2 LibKipi: 0.3.0 Operations that cause the freeze: 1. Importing picture. The import process gets to almost 100% but doesn't quite make it. 2. Free rotation. I think it's at the point where I accept the rotation but I'm currently working through some more pictures to check this. I'll report back definitely shortly. Running "gdb digikam", I've managed to capture what's visible on the photograph of the screen I'll attach after saving this text. Cheers Tony Green
Created attachment 34325 [details] end of output from "gdb digikam" Unfortunately a photograph of the screen rather than a proper screen-scrape, due to the way it's failing.
LibExiv2: 0.18 ==> i recommend to use last Exiv2 0.18.1, to be sure... LibKdcraw: 0.4.2 => A little bit old. this is the lead RAW interface for digiKam. LibRaw: 0.6.15-Release This one is the MUST important. it's integrated into libkdcraw as well (no external package) .this is the core component to handle RAW in all ways. With current code of libkdcraw (integrated with KDE/Kdegraphics component, libraw version is 0.7.2. I recomment to take a look to update it. Gilles Caulier
The freeze become during conversion to RGB color space by LibRaw. I recommend highly to update libkdcraw (which include libraw) Gilles Caulier
Many thanks for your help Gilles. It looks like Kubuntu may be installing the wrong versions. I'll investigate your recommendations and report the results here (and raise a bug with Kubuntu if that turns out to be right) Cheers Tony
digiKam 1.0.0 is out since few days... http://www.digikam.org/drupal/node/491 Please try with this version comming with more than 400 bugfixes. Thanks in advance Gilles Caulier
digiKam 1.0.0 is out since few days... http://www.digikam.org/drupal/node/491 Please try with this version coming with more than 400 bug-fixes. Thanks in advance Gilles Caulier
digiKam 1.1. release will be done in few days. Please check if this entry still valid. Thanks in advance Gilles Caulier
digiKam and Kipi-plugins 1.2.0 are out. Please check if crash is still valid there. Thanks in advance Gilles Caulier
We need more recent feedback using digiKam 1.4.0 Gilles Caulier
New digiKam 4.11.0 is available. https://www.digikam.org/node/740 Can you reproduce the problem with this release ?
This problem is not reproducible with last 5.0.0 I close this file now. Re-open it is necessary. Gilles Caulier