https://bugs.kde.org/show_bug.cgi?id=360714
Maik Qualmann changed:
What|Removed |Added
Resolution|--- |FIXED
Version Fixed In|
https://bugs.kde.org/show_bug.cgi?id=360714
--- Comment #30 from Ulrich Eckhardt ---
Comment on attachment 97969
--> https://bugs.kde.org/attachment.cgi?id=97969
Generated jp2000
I have reread the metadata and also copied the example image manually to a new
folder. But the problem still
https://bugs.kde.org/show_bug.cgi?id=360714
--- Comment #29 from caulier.gil...@gmail.com ---
F5 is not enough. Your must re-read metadata from image to store on database.
Remember that image info are cached in database to prevent to re-read image
data which an be time consuming.
Use menu entry
https://bugs.kde.org/show_bug.cgi?id=360714
--- Comment #28 from Ulrich Eckhardt ---
Created attachment 158326
--> https://bugs.kde.org/attachment.cgi?id=158326=edit
Screenshot digiKam 8.0.0 showing the size 0x0
I have retested this problem with the 8.0.0 app-image on a SuSE Leap 15.4. The
https://bugs.kde.org/show_bug.cgi?id=360714
--- Comment #27 from caulier.gil...@gmail.com ---
@Ulrich
digiKam 8.0.0 is released. This file still valid ?
Gilles Caulier
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=360714
--- Comment #26 from caulier.gil...@gmail.com ---
Git commit febc26188fe4e6037e5c8a9b1840f65729972a47 by Gilles Caulier.
Committed on 06/04/2022 at 20:38.
Pushed by cgilles into branch 'master'.
Add ExifTool backend to load metadata for image or video.
https://bugs.kde.org/show_bug.cgi?id=360714
--- Comment #25 from caulier.gil...@gmail.com ---
Git commit 5b097916d8bfa42fef5a2966fa3b34d0793cf0e2 by Gilles Caulier.
Committed on 26/04/2021 at 11:02.
Pushed by cgilles into branch 'master'.
separate ExitTool parser and process classes internal
https://bugs.kde.org/show_bug.cgi?id=360714
--- Comment #24 from caulier.gil...@gmail.com ---
Git commit 183a05476b1fa485e5143e0bb28d84e3a8daa471 by Gilles Caulier.
Committed on 26/04/2021 at 09:08.
Pushed by cgilles into branch 'master'.
Remove obsolete ExifToolTranslator class. We use now the
https://bugs.kde.org/show_bug.cgi?id=360714
--- Comment #23 from caulier.gil...@gmail.com ---
Git commit b3c56d4cdedb4ad83c7baca89c32d011f1738090 by Gilles Caulier.
Committed on 26/04/2021 at 08:58.
Pushed by cgilles into branch 'master'.
Use EXV container to translate automatically all metadata
https://bugs.kde.org/show_bug.cgi?id=360714
caulier.gil...@gmail.com changed:
What|Removed |Added
Component|Preview-Image |Metadata-ExifTool
--
You are
https://bugs.kde.org/show_bug.cgi?id=360714
caulier.gil...@gmail.com changed:
What|Removed |Added
Summary|JPGEG2000 thumbnails shows |JPGEG2000 thumbnails shows
https://bugs.kde.org/show_bug.cgi?id=360714
caulier.gil...@gmail.com changed:
What|Removed |Added
Version|5.0.0 |7.0.0
--
You are receiving this
https://bugs.kde.org/show_bug.cgi?id=360714
--- Comment #21 from Ulrich Eckhardt ---
I have retested this problem with the 7.0.0 app-image on a SuSE Leap 15.2. The
problem is still present. The Exif information is not displayed and the Image
dimension is displayed with 0x0. I have reproduced
https://bugs.kde.org/show_bug.cgi?id=360714
--- Comment #20 from caulier.gil...@gmail.com ---
digiKam 7.0.0 stable release is now published:
https://www.digikam.org/news/2020-07-19-7.0.0_release_announcement/
We need a fresh feedback on this file using this version.
Best Regards
Gilles
https://bugs.kde.org/show_bug.cgi?id=360714
--- Comment #19 from caulier.gil...@gmail.com ---
As i can see, the japser API is not wrapper by C++ exception handler (as with
Exiv2 and dmetadata interface). This is why digiKam crash.
https://bugs.kde.org/show_bug.cgi?id=360714
--- Comment #18 from caulier.gil...@gmail.com ---
The exception is generated by libjasper:
#1 0x0033b200f52e in jas_image_clearfmts () from
/tmp/.mount_oWT4Ia/usr/lib/libjasper.so.4
So, the way to decode image from jp2kloader.cpp must wrap C++
https://bugs.kde.org/show_bug.cgi?id=360714
--- Comment #17 from Maik Qualmann ---
We do not load JP2 images during scanning new images, see comment, therefore
0x0 size.
https://cgit.kde.org/digikam.git/tree/libs/dimg/loaders/jp2kloader.cpp#n97
Maik
--
You are
https://bugs.kde.org/show_bug.cgi?id=360714
--- Comment #16 from Ulrich Eckhardt ---
Here is an other backtrace of a core. I am not sure if the first one was really
the crash, there was probably an exception.
Thread 56 "Thread (pooled)" received signal SIGSEGV,
https://bugs.kde.org/show_bug.cgi?id=360714
--- Comment #15 from Ulrich Eckhardt ---
Created attachment 103879
--> https://bugs.kde.org/attachment.cgi?id=103879=edit
Screenshot of DigiKam showing size 0x0
I could see this problem here with the jp2 image already attached
https://bugs.kde.org/show_bug.cgi?id=360714
--- Comment #14 from caulier.gil...@gmail.com ---
Can you share some JP2 sample to try to reproduce here... Please use a cloud
web service please ?
Gilles Caulier
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=360714
--- Comment #13 from Ulrich Eckhardt ---
I have added the following printf statement at the end of jp2kloader.cpp
(around line 570), and there the image width and height is always printed
correctly:
jas_cleanup();
https://bugs.kde.org/show_bug.cgi?id=360714
--- Comment #12 from Ulrich Eckhardt ---
Disabling color management does not change anything. Could you give me a hint,
which file is responsible for loading jpeg2000 maybe I could do some debugging.
Log without color management:
https://bugs.kde.org/show_bug.cgi?id=360714
--- Comment #11 from caulier.gil...@gmail.com ---
digikam.dimg: LCMS internal error: cannot create a color transform instance
Color Management is enabled with thumbnails view. This is broken (wrong CM
settings in digiKam ?)
Disable CM and try again.
https://bugs.kde.org/show_bug.cgi?id=360714
--- Comment #10 from Ulrich Eckhardt ---
Created attachment 103876
--> https://bugs.kde.org/attachment.cgi?id=103876=edit
Full log of AppImage 5.5.0 from a console
The following output could be seen on the console (a full log
https://bugs.kde.org/show_bug.cgi?id=360714
--- Comment #9 from caulier.gil...@gmail.com ---
Run the AppImage 5.5.0 from a console, go to an album with JP2 image and press
F5 to force to rebuild thumbs. Report all traces from the console in this file.
Gilles Caulier
--
You are receiving this
https://bugs.kde.org/show_bug.cgi?id=360714
--- Comment #8 from Ulrich Eckhardt ---
After upgrading my system I could now test this problem against digikam 5.4.
There the problem is still present. I have also tested this now with the
appimage for pre 5.5 found on your link.
https://bugs.kde.org/show_bug.cgi?id=360714
--- Comment #7 from caulier.gil...@gmail.com ---
What's about this file using digiKam AppImage bundle 5.4.0 pre release given at
this url :
https://drive.google.com/drive/folders/0BzeiVr-byqt5Y0tIRWVWelRJenM
Gilles Caulier
--
You are receiving this
https://bugs.kde.org/show_bug.cgi?id=360714
caulier.gil...@gmail.com changed:
What|Removed |Added
Severity|minor |normal
--
You are receiving this
https://bugs.kde.org/show_bug.cgi?id=360714
caulier.gil...@gmail.com changed:
What|Removed |Added
Version|4.14.0 |5.0.0
--
You are receiving this
https://bugs.kde.org/show_bug.cgi?id=360714
--- Comment #6 from Ulrich Eckhardt ---
Seems still valid.
I couldn’t find an official digikam5 package for OpenSUSE 13.2 and I was also
not able to compile it there due to missing dependencys. But I found a
repository by wolfi.
https://bugs.kde.org/show_bug.cgi?id=360714
--- Comment #5 from caulier.gil...@gmail.com ---
This file still valid using last digiKam 5.0.0 ?
Gilles Caulier
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=360714
caulier.gil...@gmail.com changed:
What|Removed |Added
CC||caulier.gil...@gmail.com
--- Comment
https://bugs.kde.org/show_bug.cgi?id=360714
--- Comment #3 from Ulrich Eckhardt ---
Created attachment 97969
--> https://bugs.kde.org/attachment.cgi?id=97969=edit
Generated jp2000
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=360714
--- Comment #2 from Ulrich Eckhardt ---
At least exif tool displays the folllowing metadata, but this metadata is not
displayed in the metadata tab:
uli:~/Pictures # exiftool a_100.jp2
ExifTool Version Number : 9.76
https://bugs.kde.org/show_bug.cgi?id=360714
Maik Qualmann changed:
What|Removed |Added
CC||metzping...@gmail.com
35 matches
Mail list logo