Version: 0.10.0 (using 4.2.2 (KDE 4.2.2), Kubuntu packages) Compiler: cc OS: Linux (x86_64) release 2.6.28-15-generic This Backtrace is not useable Probably your KDE Package have been made in a way that does not allow good backtraces to be made, or the stackframe was severely damaged during getting stuck of the program
What is that ? Gilles Caulier
If you can reproduce the crash at will, may you read http://techbase.kde.org/Development/Tutorials/Debugging/How_to_create_useful_crash_reports and post a complete backtrace here? Thanks
Dear Dario and Gilles, i've tried to import all pictures from my external harddisk (wd 120GB) when it crashed. Now i've tried again, but the pc wan't start. I'll try to reproduce asap Nico > From: andresbajotierra@gmail.com > To: inloggegevens@live.nl > Subject: [Bug 205250] Digikam unknown crash without backtrace. > Date: Fri, 28 Aug 2009 20:08:06 +0200 > > https://bugs.kde.org/show_bug.cgi?id=205250 > > > Dario Andres <andresbajotierra@gmail.com> changed: > > What |Removed |Added > ---------------------------------------------------------------------------- > Status|UNCONFIRMED |NEEDSINFO > CC| |andresbajotierra@gmail.com > Resolution| |BACKTRACE > Summary|Deze backtrace is |Digikam unknown crash > |onbruikbaar. Mogelijk zijn |without backtrace. > |uw KDE-pakketten gemaakt op | > |een wijze die verhindert | > |dat er goede backtraces | > |kunnen worden aangemaakt, | > |of de stack frame was flink | > |beschadigd tijdens het | > |vastlopen van het | > |programma. | > > > > > --- Comment #2 from Dario Andres <andresbajotierra gmail com> 2009-08-28 20:08:05 --- > If you can reproduce the crash at will, may you read > http://techbase.kde.org/Development/Tutorials/Debugging/How_to_create_useful_crash_reports > and post a complete backtrace here? Thanks > > -- > Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email > ------- You are receiving this mail because: ------- > You reported the bug. _________________________________________________________________ 25GB gratis online harde schijf http://skydrive.live.com
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. Re-open it if necessary. Gilles Caulier