https://bugs.kde.org/show_bug.cgi?id=354819
Maik Qualmann changed:
What|Removed |Added
Resolution|--- |FIXED
https://bugs.kde.org/show_bug.cgi?id=354819
--- Comment #16 from Gernot Hillier ---
We should probably continue discussion in bug 375483, so that others can find
this information, too, right?
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=354819
--- Comment #15 from Maik Qualmann ---
Right, the first import was the problem. We read though no XMP data exists an
XMP key. Exiv2 returns the Exif key for this, but we will not check it there.
My last commit fixes this issue.
https://bugs.kde.org/show_bug.cgi?id=354819
--- Comment #14 from Gernot Hillier ---
Ok, I'm one large step ahead: all problematic images are internally tagged as
"Original Version" despite I surely never edited those files:
sqlite> select * from ImageTags where imageid in
https://bugs.kde.org/show_bug.cgi?id=354819
--- Comment #13 from Gernot Hillier ---
(In reply to Maik Qualmann from comment #11)
> Can you provide a test image from this smartphone?
>
> Maik
I already attached it, see attachment 109454. Do you need further images?
https://bugs.kde.org/show_bug.cgi?id=354819
--- Comment #12 from Maik Qualmann ---
Git commit 9a59b9d72b4d7606cf2bdb52be12a91fd22dbf21 by Maik Qualmann.
Committed on 21/12/2017 at 07:19.
Pushed by mqualmann into branch 'master'.
fix search or the Uuid if no XMP available
https://bugs.kde.org/show_bug.cgi?id=354819
Maik Qualmann changed:
What|Removed |Added
CC||metzping...@gmail.com
https://bugs.kde.org/show_bug.cgi?id=354819
--- Comment #10 from Gernot Hillier ---
Just to make this clear: touching a problematic file while digikam is running
leads to a rescan and the file is found according to debug output (see my last
comment), but it still does NOT
https://bugs.kde.org/show_bug.cgi?id=354819
--- Comment #9 from Gernot Hillier ---
Unfortunately, 5.8.0 pre-release as of today does NOT fix the issue for me. I
still have photos which are not shown by digikam. Also, I don't think this is
directly connected to bug 375483 any
https://bugs.kde.org/show_bug.cgi?id=354819
--- Comment #8 from caulier.gil...@gmail.com ---
I recommend to test with 5.8.0 pre-release Linux AppImage bundle where some
code have been fixed around the non single image ID provided by Samsung camera.
File is here :
https://files.kde.org/digikam/
https://bugs.kde.org/show_bug.cgi?id=354819
--- Comment #7 from Gernot Hillier ---
Ok, after checking the digikam debug output on stdout, I found that digikam
says this when the problematic image is added:
digikam.database: Recognized
https://bugs.kde.org/show_bug.cgi?id=354819
--- Comment #6 from Gernot Hillier ---
Created attachment 109454
--> https://bugs.kde.org/attachment.cgi?id=109454=edit
testcase for picture missing from preview list
Test picture, can be displayed with gthumb, dolphin, GIMP, etc.
https://bugs.kde.org/show_bug.cgi?id=354819
Gernot Hillier changed:
What|Removed |Added
CC||ger...@hillier.de
---
https://bugs.kde.org/show_bug.cgi?id=354819
--- Comment #4 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=354819
--- Comment #3 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.
15 matches
Mail list logo