Summary: | Kioslave crashes during batch rename | ||
---|---|---|---|
Product: | [Applications] digikam | Reporter: | Martin Foster <fido250333-kdebugs> |
Component: | AdvancedRename-engine | Assignee: | Digikam Developers <digikam-bugs-null> |
Status: | RESOLVED FIXED | ||
Severity: | crash | CC: | anantapalani, caulier.gilles |
Priority: | NOR | ||
Version: | 1.7.0 | ||
Target Milestone: | --- | ||
Platform: | Microsoft Windows | ||
OS: | Microsoft Windows | ||
Latest Commit: | Version Fixed In: | 5.0.0 | |
Sentry Crash Report: |
Description
Martin Foster
2011-01-03 21:16:51 UTC
We need more information about. Into KDE bin dir, there are some programs to use : 1/ Run kdebugdialog and turn on right digiKam/kipi debug spaces. 2/ Before to run digiKam, run debugview program to see all debug messages printed by KDE and digiKam . This is similar of console trace. 3/ Reproduce the trace and post here all debug trace for investiguation. Gilles Caulier OK, I've done that and I have numerous traces here because I'm having LOTS of trouble: [1] The batch rename job completes without any problems whatsoever. [2] The batch rename job completes but Kioslave crashes during the job. [3] The batch rename job does NOT complete because digiKam crashes! Which trace(s) do you want? I've just noticed something: Currently, I don't have digiKam running but I have 12 instances of kioslave.exe running - eh??!! (In reply to comment #1) > We need more information about. Into KDE bin dir, there are some programs to > use : > > 1/ Run kdebugdialog and turn on right digiKam/kipi debug spaces. > > 2/ Before to run digiKam, run debugview program to see all debug messages > printed by KDE and digiKam . This is similar of console trace. > > 3/ Reproduce the trace and post here all debug trace for investiguation. > > Gilles Caulier I've selected 3 traces for you to have a look at but they're far too big to post here, so I've zip'd them up and put the zip archive in my dropbox for you (or anybody else) to download. Here's the link: http://dl.dropbox.com/u/9712127/windows/Projects/digiKam-Windows/digikam_traces_01.zip The best thing would be to ignore media types that are not images in the progress bar dialog. The problem with crashing could arise in other places, too. Gilles, what do you think? Should we just skip displaying a thumbnail for video, audio and other types when showing the graphical progress bar dialog? Andi This file still valid using digiKam 2.3.0 for windows ? Gilles Caulier (In reply to comment #4) > (In reply to comment #1) > > We need more information about. Into KDE bin dir, there are some programs to > > use : > > > > 1/ Run kdebugdialog and turn on right digiKam/kipi debug spaces. > > > > 2/ Before to run digiKam, run debugview program to see all debug messages > > printed by KDE and digiKam . This is similar of console trace. > > > > 3/ Reproduce the trace and post here all debug trace for investiguation. > > > > Gilles Caulier > > I've selected 3 traces for you to have a look at but they're far too big to > post here, so I've zip'd them up and put the zip archive in my dropbox for > you (or anybody else) to download. > > Here's the link: > http://dl.dropbox.com/u/9712127/windows/Projects/digiKam-Windows/ > digikam_traces_01.zip Hi Martin, Could you try this out with digiKam 3.1.0? A lot of changes were made in regard to renaming files and temporary file names: http://download.kde.org/stable/digikam/digiKam-installer-3.1.0-win32.exe New digiKam 4.11.0 is available : https://www.digikam.org/node/740 Can you reproduce the problem with this release ? digiKam 4.11.0 Windows installer is available for download : http://download.kde.org/stable/digikam/digiKam-installer-4.11.0-win32.exe.mirrorlist digiKam 4.12.0 is out : https://www.digikam.org/node/741 We need a fresh feedback using this release please... Thanks in advance. With next digiKam 5.0.0, we will provide a fully cross-compiled version Windows under Linux where a lots of problems have been fixed. https://www.flickr.com/photos/digikam/27033685570/in/dateposted-public/ The Windows installer is available here to test : https://drive.google.com/open?id=0B7yq-xFihT0_SzhxVzF1RDhPbFE Gilles Caulier |