https://bugs.kde.org/show_bug.cgi?id=384603
Maik Qualmann changed:
What|Removed |Added
Resolution|--- |FIXED
Version Fixed
https://bugs.kde.org/show_bug.cgi?id=384603
Simon changed:
What|Removed |Added
CC||freisi...@gmail.com
--- Comment
https://bugs.kde.org/show_bug.cgi?id=384603
--- Comment #13 from digi...@homemp3.dyndns.org ---
Even simpler: I found out that simply touching the file (updating the last
modified timestamp in the file system, using the "touch" command) and then
re-reading the metadata from file gives the file
https://bugs.kde.org/show_bug.cgi?id=384603
--- Comment #12 from digi...@homemp3.dyndns.org ---
I did another experiment: when I open one of the JPG files affected with GIMP
and simply export it again as JPG, keeping all EXIF information, the timestamp
is updated property when refreshing the
https://bugs.kde.org/show_bug.cgi?id=384603
--- Comment #11 from digi...@homemp3.dyndns.org ---
I've now switched back to the old DB where at least all my tags seem to be
complete again. The log output digikam gives when doing "Item - Reread metadata
from file" on an item where the camera
https://bugs.kde.org/show_bug.cgi?id=384603
--- Comment #10 from digi...@homemp3.dyndns.org ---
Checking the results of the DB-reconstruction shows that certain tags got lost
which is a showstopper for me. Pictures that have to tags in the EXIF info
containe in the file only show one of the two
https://bugs.kde.org/show_bug.cgi?id=384603
--- Comment #9 from digi...@homemp3.dyndns.org ---
I now re-created the DB for the whole collection, and the timestamps have
properly shown up. What does that tell us?
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=384603
--- Comment #8 from digi...@homemp3.dyndns.org ---
Created attachment 107824
--> https://bugs.kde.org/attachment.cgi?id=107824=edit
Screenshot documenting the viewer settings
The viewer settings are such that the Camera Creation Date shall be shown.
https://bugs.kde.org/show_bug.cgi?id=384603
--- Comment #7 from digi...@homemp3.dyndns.org ---
(In reply to Maik Qualmann from comment #6)
> The problem is if the date can not be read from the metadata, the file date
> is used. An empty date can not actually occur.
You can see from the
https://bugs.kde.org/show_bug.cgi?id=384603
--- Comment #6 from Maik Qualmann ---
The problem is if the date can not be read from the metadata, the file date is
used. An empty date can not actually occur. I have here times my collection
with 40k images imported into an
https://bugs.kde.org/show_bug.cgi?id=384603
--- Comment #5 from digi...@homemp3.dyndns.org ---
I can try that. It's roughly a 130k images collection, and the DB is running on
a different host on the local network, so it'll take a while to re-build the
DB, I presume. Just out of curiosity: if that
https://bugs.kde.org/show_bug.cgi?id=384603
--- Comment #4 from Maik Qualmann ---
Can you create a new MySQL DB for test purposes and check if the problem still
exists?
Maik
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=384603
--- Comment #3 from digi...@homemp3.dyndns.org ---
So, is this still the correct component for the report? Or is there a separate
one for the MySQL connector?
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=384603
Maik Qualmann changed:
What|Removed |Added
CC||metzping...@gmail.com
https://bugs.kde.org/show_bug.cgi?id=384603
--- Comment #1 from digi...@homemp3.dyndns.org ---
Nota bene: I'm using digikam with the MySQL connector, if that changes
anything.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=384603
digi...@homemp3.dyndns.org changed:
What|Removed |Added
Attachment #107807|Screenshot showing how |Screenshot showing how
16 matches
Mail list logo