[Bug 303992] New: Digikam is closing after opening any file dialog

[Rafael]

https://bugs.kde.org/show_bug.cgi?id=303992

            Bug ID: 303992
          Severity: critical
           Version: 2.7.0
          Priority: NOR
          Assignee: [hidden email]
           Summary: Digikam is closing after opening any file dialog
    Classification: Unclassified
                OS: MS Windows
          Reporter: [hidden email]
          Hardware: MS Windows
            Status: UNCONFIRMED
         Component: general
           Product: digikam

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

--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

[Gilles Caulier-4]

https://bugs.kde.org/show_bug.cgi?id=303992

Gilles Caulier <[hidden email]> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |RESOLVED
                 CC|                            |[hidden email]
         Resolution|---                         |WAITINGFORINFO

--- Comment #1 from Gilles Caulier <[hidden email]> ---
We need  a debugger backtrace please...
Gilles caulier

--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

[Rafael]

https://bugs.kde.org/show_bug.cgi?id=303992

--- Comment #2 from Rafael <[hidden email]> ---
I don't have gdb (is NOT included in the installation) and didn't use it
before. Could you guide me , please?

--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

[Rafael]

https://bugs.kde.org/show_bug.cgi?id=303992

--- Comment #3 from Rafael <[hidden email]> ---
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

--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

[Rafael]

https://bugs.kde.org/show_bug.cgi?id=303992

--- Comment #4 from Rafael <[hidden email]> ---
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

--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

[Rafael]

https://bugs.kde.org/show_bug.cgi?id=303992

--- Comment #5 from Rafael <[hidden email]> ---
Please, no one will help me then?

--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

[Gilles Caulier-4]

https://bugs.kde.org/show_bug.cgi?id=303992

--- Comment #6 from Gilles Caulier <[hidden email]> ---
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

--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

[Rafael]

https://bugs.kde.org/show_bug.cgi?id=303992

--- Comment #7 from Rafael <[hidden email]> ---
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

--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

[Gilles Caulier-4]

https://bugs.kde.org/show_bug.cgi?id=303992

--- Comment #8 from Gilles Caulier <[hidden email]> ---
Perhaps it's not the right version of DLL

Gilles Caulier

--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

[Andrew Goodbody]

https://bugs.kde.org/show_bug.cgi?id=303992

Andrew Goodbody <[hidden email]> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[hidden email]

--- Comment #9 from Andrew Goodbody <[hidden email]> ---
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 the assignee for the bug.
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

[Rafael]

https://bugs.kde.org/show_bug.cgi?id=303992

--- Comment #10 from Rafael <[hidden email]> ---
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 <[hidden email]>

> https://bugs.kde.org/show_bug.cgi?id=303992
>
> Andrew Goodbody <[hidden email]> changed:
>
>            What    |Removed                     |Added
>
> ----------------------------------------------------------------------------
>                  CC|                            |[hidden email]
>
> --- Comment #9 from Andrew Goodbody <[hidden email]> ---
> 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.
>

--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

[Rafael]

https://bugs.kde.org/show_bug.cgi?id=303992

--- Comment #11 from Rafael <[hidden email]> ---
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.

--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

[Gilles Caulier-4]

https://bugs.kde.org/show_bug.cgi?id=303992

Gilles Caulier <[hidden email]> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[hidden email]

--- Comment #12 from Gilles Caulier <[hidden email]> ---
Ananta,

Any idea about the problem under windows DLL ?

Gilles Caulier

--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

[Rafael]

https://bugs.kde.org/show_bug.cgi?id=303992

--- Comment #13 from Rafael <[hidden email]> ---
I have no idea about Windows libraries. Could it be related to x64
platform? Is digikam working right on Windows x64?

--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

[Gilles Caulier-4]

https://bugs.kde.org/show_bug.cgi?id=303992

--- Comment #14 from Gilles Caulier <[hidden email]> ---
yes, it run fine on my Toshiba Z830 Win7 64bits ultrabook...

Gilles Caulier

--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

[Rafael]

https://bugs.kde.org/show_bug.cgi?id=303992

--- Comment #15 from Rafael <[hidden email]> ---
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.

:(

--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

[Ananta Palani]

https://bugs.kde.org/show_bug.cgi?id=303992

--- Comment #16 from Ananta Palani <[hidden email]> ---
(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.

--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

[Rafael]

https://bugs.kde.org/show_bug.cgi?id=303992

--- Comment #17 from Rafael <[hidden email]> ---
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.

--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

[Rafael]

https://bugs.kde.org/show_bug.cgi?id=303992

--- Comment #18 from Rafael <[hidden email]> ---
Created attachment 73020
  --> https://bugs.kde.org/attachment.cgi?id=73020&action=edit
Last image before Digikam is automatically closed

I detached logical drives, but it did not solve the problem.

:(

--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

[Gilles Caulier-4]

https://bugs.kde.org/show_bug.cgi?id=303992

--- Comment #19 from Gilles Caulier <[hidden email]> ---
New digiKam 4.11.0 is available :

https://www.digikam.org/node/740

Can you reproduce the problem with this release ?

Gilles Caulier

--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel