https://bugs.kde.org/show_bug.cgi?id=471797
caulier.gil...@gmail.com changed:
What|Removed |Added
Version Fixed In||8.2.0
Resolution|DUPLICATE
https://bugs.kde.org/show_bug.cgi?id=471797
--- Comment #22 from Maik Qualmann ---
Git commit ab3e2e5adb8d9e51cda6973e57828569dff21141 by Maik Qualmann.
Committed on 23/07/2023 at 07:46.
Pushed by mqualmann into branch 'master'.
try new settings to compile libaom
Related: bug 471269, bug 472508
https://bugs.kde.org/show_bug.cgi?id=471797
--- Comment #21 from dnovome...@gmail.com ---
Today I tried digiKam-8.2.0-20230720T094929-Win64.exe and I am still getting
the crash.
I was curios to see if the
https://invent.kde.org/graphics/digikam/-/commit/c977031ec78cf2d914b5c163b3a8be9cf09e4000
https://bugs.kde.org/show_bug.cgi?id=471797
--- Comment #20 from caulier.gil...@gmail.com ---
Git commit c977031ec78cf2d914b5c163b3a8be9cf09e4000 by Gilles Caulier.
Committed on 04/07/2023 at 03:44.
Pushed by cgilles into branch 'master'.
add new option to compile AOM under MinGW
M +9-0
https://bugs.kde.org/show_bug.cgi?id=471797
--- Comment #19 from dnovome...@gmail.com ---
-DAOM_TARGET_CPU=generic completely disables assembler optimization. It will
make the library very slow but It would be good to make that experiment to see
if it helps.
What about trying to avoid in-source
https://bugs.kde.org/show_bug.cgi?id=471797
--- Comment #18 from Maik Qualmann ---
I think we need to set the compile option "-DAOM_TARGET_CPU=generic".
Otherwise, the compiling system's CPU is used.
Maik
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=471797
--- Comment #17 from caulier.gil...@gmail.com ---
yes it is, including all shared libs and the whole KF5 frameworks (eg
KImageFormat).
Gilles
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=471797
--- Comment #16 from Maik Qualmann ---
Hmm, I have neither a crash in my VM on Windows 10 (AMD), nor on a real Windows
10 machine with Intel I5.
Gilles added version 3.61 of libaom relatively recently. The question is, has
the MXE stage been
https://bugs.kde.org/show_bug.cgi?id=471797
dnovome...@gmail.com changed:
What|Removed |Added
CC||dnovome...@gmail.com
--- Comment #15
https://bugs.kde.org/show_bug.cgi?id=471797
Maik Qualmann changed:
What|Removed |Added
Status|REPORTED|RESOLVED
Resolution|---
https://bugs.kde.org/show_bug.cgi?id=471797
--- Comment #13 from philip_ram...@hotmail.com ---
Created attachment 160033
--> https://bugs.kde.org/attachment.cgi?id=160033=edit
86.avif file which reliably causes DigiKam to crash
I deleted the D:\temp\86.avif file and it does indeed appear to be
https://bugs.kde.org/show_bug.cgi?id=471797
--- Comment #12 from Maik Qualmann ---
In the first log, "D:/Temp/86.avif" was the last file scanned. The AVIF file
could be the problem.
Maik
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=471797
--- Comment #11 from Maik Qualmann ---
Ok, please create a new log.
Maik
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=471797
--- Comment #10 from philip_ram...@hotmail.com ---
Many thanks.
I have deleted the file "P:/thumbnails-digikam.db" - but DigiKam still crashes
at 74% when I start it.
I also don't have enough time to make any changes in Settings before DigiKam
crashes
https://bugs.kde.org/show_bug.cgi?id=471797
--- Comment #9 from Maik Qualmann ---
Oh, what binary data is there in the log, your thumbnail database is broken.
The thumbnail database can no longer be repaired with the error number, delete
the file "P:/thumbnails-digikam.db". The database is
https://bugs.kde.org/show_bug.cgi?id=471797
--- Comment #8 from philip_ram...@hotmail.com ---
Created attachment 160017
--> https://bugs.kde.org/attachment.cgi?id=160017=edit
DebugView log from debug version of DigiKam
Thanks.
I just realised that I was running
https://bugs.kde.org/show_bug.cgi?id=471797
--- Comment #7 from Maik Qualmann ---
The variable seems to be set correctly. We recently had the same issue of not
being able to turn on debug output. I need to test if it is related to
Windows11.
Maik
--
You are receiving this mail because:
You
https://bugs.kde.org/show_bug.cgi?id=471797
--- Comment #6 from philip_ram...@hotmail.com ---
Have added screenshots from Control Panel and from sysinfo32 which appear to
show that QT_LOGGING_RULES is set to digikam*=true.
Am I doing something wrong? I'm still getting the same output from
https://bugs.kde.org/show_bug.cgi?id=471797
--- Comment #5 from philip_ram...@hotmail.com ---
Created attachment 160008
--> https://bugs.kde.org/attachment.cgi?id=160008=edit
msinfo32
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=471797
--- Comment #4 from philip_ram...@hotmail.com ---
Created attachment 160007
--> https://bugs.kde.org/attachment.cgi?id=160007=edit
Control Panel > System > Advanced
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=471797
--- Comment #3 from Maik Qualmann ---
The log shows no debug messages, only minor warnings.
The Qt debug variable is not set correctly in the Windows environment variable
editor:
This entries must be entered as user environment variables, without the
https://bugs.kde.org/show_bug.cgi?id=471797
--- Comment #2 from philip_ram...@hotmail.com ---
Created attachment 160006
--> https://bugs.kde.org/attachment.cgi?id=160006=edit
DebugView Log
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=471797
Maik Qualmann changed:
What|Removed |Added
CC||metzping...@gmail.com
--- Comment #1 from Maik
https://bugs.kde.org/show_bug.cgi?id=471797
caulier.gil...@gmail.com changed:
What|Removed |Added
OS|Other |Microsoft Windows
https://bugs.kde.org/show_bug.cgi?id=471797
Bug Janitor Service changed:
What|Removed |Added
Severity|critical|crash
--
You are receiving this mail
25 matches
Mail list logo
