After installing digikam standalone version (that have no gtb), if I try to launch a selection dialog, like to add a new album, digikam is closed. It happen with ANY program with file dialog window from "digikam/bin", as with "dngconverter.exe", when I press "`+" to add files to convert. I'm using Win 7. Reproducible: Always Steps to Reproduce: 1.Launch digikam 2.Try to add a new Album 3.A file dialog appear ("Select the folder ....") and inmediately, digikam is closed. Actual Results: digikam is closed Expected Results: Browse acroos folders tree to select any folders / files
We need a debugger backtrace please... Gilles caulier
I don't have gdb (is NOT included in the installation) and didn't use it before. Could you guide me , please?
I tried to debug with WinDbg, with 2 options, "Open executable" and "Attach to process", but this is what I got .... ModLoad: 00000000`58ea0000 00000000`58ecf000 digikamimageplugin_fxfilters.dll ModLoad: 00000000`58e40000 00000000`58e91000 digikamimageplugin_transform.dll (1404.1f7c): Break instruction exception - code 80000003 (first chance) *** ERROR: Symbol file could not be found. Defaulted to export symbols for C:\Windows\SYSTEM32\ntdll.dll - ntdll!DbgBreakPoint: 00000000`76d70530 cc int 3
That was with "Attach to process" from WinDBG (so I can't get to open any dialog cause WinDBG blocked digikam). With "Open executable", this is what I got (and digikam doesn't appear) Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64 Copyright (c) Microsoft Corporation. All rights reserved. CommandLine: "C:\Program Files (x86)\digiKam\bin\digikam.exe" Symbol search path is: *** Invalid *** **************************************************************************** * Symbol loading may be unreliable without a symbol search path. * * Use .symfix to have the debugger choose a symbol path. * * After setting your symbol path, use .reload to refresh symbol locations. * **************************************************************************** Executable search path is: ModLoad: 00000000`012d0000 00000000`0172b000 digikam.exe ModLoad: 00000000`76d20000 00000000`76ec9000 ntdll.dll ModLoad: 00000000`76f00000 00000000`77080000 ntdll32.dll ModLoad: 00000000`74580000 00000000`745bf000 C:\Windows\SYSTEM32\wow64.dll ModLoad: 00000000`74520000 00000000`7457c000 C:\Windows\SYSTEM32\wow64win.dll ModLoad: 00000000`74510000 00000000`74518000 C:\Windows\SYSTEM32\wow64cpu.dll (1b44.1fd0): Break instruction exception - code 80000003 (first chance) *** ERROR: Symbol file could not be found. Defaulted to export symbols for ntdll.dll - ntdll!CsrSetPriorityClass+0x40: 00000000`76dccb60 cc int 3
Please, no one will help me then?
Look like it miss an internal windows dll file in your system : *** ERROR: Symbol file could not be found. Defaulted to export symbols for C:\Windows\SYSTEM32\ntdll.dll - The question is why ? Gilles Caulier
I don't know why. The file is there and even in more directories (sysnow64 for example). I'm admin on this Windows 7 x64 and really have no idea what's the problem, cause I didn't use a debugger before. Thank you
Perhaps it's not the right version of DLL Gilles Caulier
The issue with ntdll.dll is that WinDbg cannot find the symbols for printing in the backtrace. You can configure WinDbg to automatically download any Windows symbols it needs. See the article at this link http://features.techworld.com/operating-systems/3275067/solving-windows-7-crashes-with-debugging-tools/?pn=2 This does not explain why the code is ending up at the breakpoint though.
Thank you Andrew. This is the result after I did what you told me. ModLoad: 00000000`013e0000 00000000`0183b000 digikam.exe ModLoad: 00000000`775a0000 00000000`77749000 ntdll.dll ModLoad: 00000000`77780000 00000000`77900000 ntdll32.dll ModLoad: 00000000`74e00000 00000000`74e3f000 C:\Windows\SYSTEM32\wow64.dll ModLoad: 00000000`74da0000 00000000`74dfc000 C:\Windows\SYSTEM32\wow64win.dll ModLoad: 00000000`74d90000 00000000`74d98000 C:\Windows\SYSTEM32\wow64cpu.dll (188c.1f9c): Break instruction exception - code 80000003 (first chance) ntdll!LdrpDoDebuggerBreak+0x30: 00000000`7764cb60 cc int 3 I don't know what's the problem neither. 2012/8/2 Andrew Goodbody <ajg02@elfringham.co.uk> > https://bugs.kde.org/show_bug.cgi?id=303992 > > Andrew Goodbody <ajg02@elfringham.co.uk> changed: > > What |Removed |Added > > ---------------------------------------------------------------------------- > CC| |ajg02@elfringham.co.uk > > --- Comment #9 from Andrew Goodbody <ajg02@elfringham.co.uk> --- > The issue with ntdll.dll is that WinDbg cannot find the symbols for > printing in > the backtrace. You can configure WinDbg to automatically download any > Windows > symbols it needs. See the article at this link > > http://features.techworld.com/operating-systems/3275067/solving-windows-7-crashes-with-debugging-tools/?pn=2 > This does not explain why the code is ending up at the breakpoint though. > > -- > You are receiving this mail because: > You are on the CC list for the bug. > You reported the bug. >
Thank you Andrew. This is the result after I did what you told me. ModLoad: 00000000`013e0000 00000000`0183b000 digikam.exe ModLoad: 00000000`775a0000 00000000`77749000 ntdll.dll ModLoad: 00000000`77780000 00000000`77900000 ntdll32.dll ModLoad: 00000000`74e00000 00000000`74e3f000 C:\Windows\SYSTEM32\wow64.dll ModLoad: 00000000`74da0000 00000000`74dfc000 C:\Windows\SYSTEM32\wow64win.dll ModLoad: 00000000`74d90000 00000000`74d98000 C:\Windows\SYSTEM32\wow64cpu.dll (188c.1f9c): Break instruction exception - code 80000003 (first chance) ntdll!LdrpDoDebuggerBreak+0x30: 00000000`7764cb60 cc int 3 I don't know what's the problem neither.
Ananta, Any idea about the problem under windows DLL ? Gilles Caulier
I have no idea about Windows libraries. Could it be related to x64 platform? Is digikam working right on Windows x64?
yes, it run fine on my Toshiba Z830 Win7 64bits ultrabook... Gilles Caulier
So we are now in a no exit road. I try again and again to lauch Digikam, but always, any time I try to open a file dialog, it appear for 2 seconds and finally, Digikam is closed. I'll give up. :(
(In reply to comment #15) > So we are now in a no exit road. I try again and again to lauch Digikam, but > always, any time I try to open a file dialog, it appear for 2 seconds and > finally, Digikam is closed. I'll give up. Do you have any external devices for plugged in, such as SD cards, USB devices, etc.? If so, try unplugging all of them and restarting your computer. Then run digiKam and test again. I'm wondering if this is related to problems some users have when starting digiKam with some external devices mounted.
Thank you Ananta. I must say that I have no one storage device to my Dell, only mouse and keyboard. But I'm agree with you. Is the fact of showing storage drives. I'm thinking on trying to unattach logical drives of my Windows net, cause that could be a cause. Thank you any way!!!!!! I will report tomorrow about this try.
Created attachment 73020 [details] Last image before Digikam is automatically closed I detached logical drives, but it did not solve the problem. :(
New digiKam 4.11.0 is available : https://www.digikam.org/node/740 Can you reproduce the problem with this release ? Gilles Caulier
Hi. Please, WHERE is available for Windows? Here http://download.kde.org/stable/digikam/ there is not version 4.11 available for Windows. Or I can't see it al least.
4.11.0 will be compiled in few days by Ananta. Else, 4.10.0 installer can be used for a first try... Gilles Caulier
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