https://bugs.kde.org/show_bug.cgi?id=415489
--- Comment #31 from ajay1...@gmail.com ---
(In reply to caulier.gilles from comment #30)
> You tested a digiKam 32 on a Windows 10 32 bits or 64 bits ?
I tested on Windows 10 32 bit.
--
You are receiving this mail because:
You are watching all bug ch
https://bugs.kde.org/show_bug.cgi?id=415489
--- Comment #30 from caulier.gil...@gmail.com ---
You tested a digiKam 32 on a Windows 10 32 bits or 64 bits ?
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=415489
--- Comment #29 from ajay1...@gmail.com ---
Created attachment 124771
--> https://bugs.kde.org/attachment.cgi?id=124771&action=edit
DebugView log for digiKam-6.4.0 crash on windows 10 while in Preview mode after
fix
--
You are receiving this mail bec
https://bugs.kde.org/show_bug.cgi?id=415489
--- Comment #28 from ajay1...@gmail.com ---
I tested digiKam-7.0.0-Beta1 32-bit on Windows 10. It still crashed after some
time. I could capture DebugView log. But while trying to capture digikam debug
log my digikam hanged and I had to kill it. I have a
https://bugs.kde.org/show_bug.cgi?id=415489
caulier.gil...@gmail.com changed:
What|Removed |Added
Version Fixed In||7.0.0
Resolution|NOT A BUG
https://bugs.kde.org/show_bug.cgi?id=415489
hardy.pub...@gmail.com changed:
What|Removed |Added
Status|REPORTED|RESOLVED
Resolution|---
https://bugs.kde.org/show_bug.cgi?id=415489
--- Comment #27 from hardy.pub...@gmail.com ---
I have Win 10 64 bit.
When the invitation went out to test 7.0.0 Beta 1, I looked at the list of
packages and saw only 32 bit:
digiKam-7.0.0-beta1-Win32.exe
But now I look harder and I see the 64 bit
https://bugs.kde.org/show_bug.cgi?id=415489
--- Comment #26 from caulier.gil...@gmail.com ---
The car ash log must be present. I already experienced some conflicts with
anti-virus stuff. Are you a virus guard enabled and n your system ?
Another Q: did you use the 32 bits or the 64 bits version on
https://bugs.kde.org/show_bug.cgi?id=415489
--- Comment #25 from hardy.pub...@gmail.com ---
(In reply to Maik Qualmann from comment #19)
> A new test version of digiKam-7.0.0-Beta1 is available. Can the crash still
> be reproduced?
>
> https://files.kde.org/digikam/
>
> Maik
The version digiKam
https://bugs.kde.org/show_bug.cgi?id=415489
--- Comment #24 from hardy.pub...@gmail.com ---
Just one side observation. The following line insists that digikam_crash.log is
output:
"warning: digikam.general: DrMinGw crash-file will be located at:
"C:\\Users\\USERNAME\\AppData\\Local\\digikam_cras
https://bugs.kde.org/show_bug.cgi?id=415489
--- Comment #23 from hardy.pub...@gmail.com ---
Also, I disabled all plugins and this makes no difference either.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=415489
--- Comment #22 from hardy.pub...@gmail.com ---
(In reply to Maik Qualmann from comment #21)
> Can you please deactivate color management in digiKam Setup and test again?
>
> Maik
With "Enable Colour Management" set to off, it makes no difference.
--
https://bugs.kde.org/show_bug.cgi?id=415489
--- Comment #21 from Maik Qualmann ---
Can you please deactivate color management in digiKam Setup and test again?
Maik
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=415489
--- Comment #20 from hardy.pub...@gmail.com ---
(In reply to Maik Qualmann from comment #14)
> The log should have been created automatically. There is another option with
> the debugger, but it is a little more difficult, let's see if you can do it.
>
https://bugs.kde.org/show_bug.cgi?id=415489
--- Comment #19 from Maik Qualmann ---
A new test version of digiKam-7.0.0-Beta1 is available. Can the crash still be
reproduced?
https://files.kde.org/digikam/
Maik
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=415489
--- Comment #18 from Maik Qualmann ---
Git commit 7fffd49c5fc9080e96af2f0bf9ce642c6c5e349a by Maik Qualmann.
Committed on 25/12/2019 at 12:11.
Pushed by mqualmann into branch 'master'.
try to fix crash on preview image
M +14 -6core/libs/dimg/lo
https://bugs.kde.org/show_bug.cgi?id=415489
--- Comment #17 from Maik Qualmann ---
We have this error message:
Qt Concurrent has caught an exception thrown from a worker thread.
This is not supported, exceptions thrown in worker threads must be
caught before control returns t
https://bugs.kde.org/show_bug.cgi?id=415489
--- Comment #16 from ajay1...@gmail.com ---
Created attachment 124701
--> https://bugs.kde.org/attachment.cgi?id=124701&action=edit
gdb digiKam log for digiKam-6.4.0 crash on windows 10 on switching to preview
mode
This log was extracted using below s
https://bugs.kde.org/show_bug.cgi?id=415489
--- Comment #15 from ajay1...@gmail.com ---
Created attachment 124700
--> https://bugs.kde.org/attachment.cgi?id=124700&action=edit
DebugView log for digiKam-6.4.0 crash on windows 10 on switching to preview
mode
I started DebugView and switched from
https://bugs.kde.org/show_bug.cgi?id=415489
--- Comment #14 from Maik Qualmann ---
The log should have been created automatically. There is another option with
the debugger, but it is a little more difficult, let's see if you can do it.
Start the CMD.exe and execute the following commands:
cd "
https://bugs.kde.org/show_bug.cgi?id=415489
--- Comment #13 from hardy.pub...@gmail.com ---
(In reply to Maik Qualmann from comment #11)
> If the file exists, it would be of interest:
>
> C:\Users\%USERNAME%\AppData\Local\digikam_crash.log
>
> Maik
No such file unfortunately. Let me know how I
https://bugs.kde.org/show_bug.cgi?id=415489
Maik Qualmann changed:
What|Removed |Added
CC||ajay1...@gmail.com
--- Comment #12 from Maik Qu
https://bugs.kde.org/show_bug.cgi?id=415489
--- Comment #11 from Maik Qualmann ---
If the file exists, it would be of interest:
C:\Users\%USERNAME%\AppData\Local\digikam_crash.log
Maik
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=415489
--- Comment #10 from hardy.pub...@gmail.com ---
Created attachment 124685
--> https://bugs.kde.org/attachment.cgi?id=124685&action=edit
AppCashView Screenshot
I looked at the Report.wer files in
C:\ProgramData\Microsoft\Windows\WER\ReportArchive with
https://bugs.kde.org/show_bug.cgi?id=415489
--- Comment #9 from hardy.pub...@gmail.com ---
I can't reliably reproduce this problem in different Windows sessions.
Restarting the PC seems to resolve the issue sometimes.
However, when the problem was present the following observations are 100%
repea
https://bugs.kde.org/show_bug.cgi?id=415489
--- Comment #8 from Maik Qualmann ---
Ok, if MinGW uses C++03 by default, then it is clear. I cannot reproduce the
crash with the test image in a Windows 10 VM.
Maik
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=415489
--- Comment #7 from caulier.gil...@gmail.com ---
MXE use G++ 5.5.0 and is compatible with C++11. We just need to force compiler
to use C++11 in CMake at configuration stage.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=415489
--- Comment #6 from caulier.gil...@gmail.com ---
Maik, look this :
https://forum.qt.io/topic/35638/issue-with-new-signal-slot-mechanism-in-mingw-qt5-2/2
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=415489
--- Comment #5 from Maik Qualmann ---
This new type of signal/slot connection can probably not be processed by MinGW.
It is not relevant for this crash, but maintenance tasks cannot currently be
canceled in the Windows version.
connect(this, static_cas
https://bugs.kde.org/show_bug.cgi?id=415489
Maik Qualmann changed:
What|Removed |Added
CC||metzping...@gmail.com
--- Comment #4 from Maik
https://bugs.kde.org/show_bug.cgi?id=415489
--- Comment #3 from hardy.pub...@gmail.com ---
The problem image is DSC_0017_1.JPG which is too large to attach but is
accessible here:
https://1drv.ms/u/s!AhmvR4JSJH8OkwwXmqk0n0yOBH7d?e=56RzXD
--
You are receiving this mail because:
You are watching a
https://bugs.kde.org/show_bug.cgi?id=415489
--- Comment #2 from hardy.pub...@gmail.com ---
Created attachment 124676
--> https://bugs.kde.org/attachment.cgi?id=124676&action=edit
Debug Log 2
I can't share those images, sorry, I should have checked before posting.
I have an image which causes t
https://bugs.kde.org/show_bug.cgi?id=415489
caulier.gil...@gmail.com changed:
What|Removed |Added
CC||caulier.gil...@gmail.com
--- Comment
33 matches
Mail list logo
