https://bugs.kde.org/show_bug.cgi?id=453165
Maik Qualmann changed:
What|Removed |Added
Status|REPORTED|RESOLVED
Resolution|---
https://bugs.kde.org/show_bug.cgi?id=453165
--- Comment #19 from Maik Qualmann ---
We have a patch from the LibRaw team:
https://github.com/LibRaw/LibRaw/issues/460
Maik
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=453165
--- Comment #18 from caulier.gil...@gmail.com ---
Note to report a UPSTREAM bug in libraw, use github project here :
https://github.com/LibRaw/LibRaw/issues
Don't forget to link to this file to pass technical information to Libraw team.
The current li
https://bugs.kde.org/show_bug.cgi?id=453165
--- Comment #17 from Maik Qualmann ---
Created attachment 148570
--> https://bugs.kde.org/attachment.cgi?id=148570&action=edit
LibRaw patch
It clearly crashes in LibRaw. However, your images are probably defective.
Please open a bug report on LibRaw
https://bugs.kde.org/show_bug.cgi?id=453165
--- Comment #16 from vfr...@gmail.com ---
Created attachment 148562
--> https://bugs.kde.org/attachment.cgi?id=148562&action=edit
Digikam's log when reproduced the steps (with newer build)
I've just downloaded the last .appimage from files.kde.org and
https://bugs.kde.org/show_bug.cgi?id=453165
--- Comment #15 from Maik Qualmann ---
The cause of your crash in your build is that the digiKam plugins are not
found. I tested it on myself and set the environment variable "DK_PLUGIN_PATH"
to an empty directory. I can then reproduce the crash, it sho
https://bugs.kde.org/show_bug.cgi?id=453165
--- Comment #14 from caulier.gil...@gmail.com ---
Sure no problem. It started now. File will be online in few hours
Gilles
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=453165
--- Comment #13 from Maik Qualmann ---
Gilles creates weekly snapshots here:
https://files.kde.org/digikam/
@Gilles, can you please start creating a new AppImage?
Maik
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=453165
--- Comment #12 from vfr...@gmail.com ---
Created attachment 148547
--> https://bugs.kde.org/attachment.cgi?id=148547&action=edit
backtrace of my own compilation with the patch
Thanks for submitting the patch. I've downloaded the code, installed all t
https://bugs.kde.org/show_bug.cgi?id=453165
--- Comment #11 from Maik Qualmann ---
Git commit 21b395f696f6d74d1970b5ad82a61e35e4284863 by Maik Qualmann.
Committed on 03/05/2022 at 18:01.
Pushed by mqualmann into branch 'qt5-maintenance'.
add image path to debug output for testing
M +2-2
https://bugs.kde.org/show_bug.cgi?id=453165
--- Comment #10 from vfr...@gmail.com ---
Created attachment 148527
--> https://bugs.kde.org/attachment.cgi?id=148527&action=edit
Digikam's log when reproduced the steps
I've enabled a more verbose logging to try to get the file that is failing, but
I
https://bugs.kde.org/show_bug.cgi?id=453165
--- Comment #9 from Maik Qualmann ---
Could the file be identified? Can you provide us the file for testing to fix
the problem?
Maik
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=453165
--- Comment #8 from Maik Qualmann ---
To see which file is affected enable full debug output in the terminal:
export QT_LOGGING_RULES="digikam.*=true"
Or if there is too much debug output of the libjpeg:
export QT_LOGGING_RULES="digikam.*=true;digika
https://bugs.kde.org/show_bug.cgi?id=453165
--- Comment #7 from caulier.gil...@gmail.com ---
To patch code, just fork digiKam project from KDE git (gitlab in background),
make change, and make a merge request.
For simple changes, all can be done through the web interface directly...
https://inve
https://bugs.kde.org/show_bug.cgi?id=453165
--- Comment #6 from caulier.gil...@gmail.com ---
We need the completed log from the console, not just the last lines.
Gilles Caulier
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=453165
--- Comment #5 from vfr...@gmail.com ---
It seems that the error may be in this call:
https://invent.kde.org/graphics/digikam/-/blob/master/core/libs/metadataengine/engine/metaengine_previews.cpp#L71
I don't have the knowledge to edit the source code (n
https://bugs.kde.org/show_bug.cgi?id=453165
--- Comment #4 from vfr...@gmail.com ---
(In reply to caulier.gilles from comment #2)
> Which kind of RAW files did you use exactly ?
>
> Can you provide the console trace (not the debug trace) ?
>
> Gilles Caulier
The console trace is specified up. I
https://bugs.kde.org/show_bug.cgi?id=453165
Maik Qualmann changed:
What|Removed |Added
CC||metzping...@gmail.com
--- Comment #3 from Maik
https://bugs.kde.org/show_bug.cgi?id=453165
caulier.gil...@gmail.com changed:
What|Removed |Added
Component|Metadata-Exif |Preview-RAW
CC|
https://bugs.kde.org/show_bug.cgi?id=453165
--- Comment #1 from vfr...@gmail.com ---
I've run again the debugger and the stacktrace is different:
```
Thread 53 "Thread (pooled)" hit Breakpoint 1, 0x73779660 in __cxa_throw
() from /lib/x86_64-linux-gnu/libstdc++.so.6
#0 0x73779660
20 matches
Mail list logo
