[digiKam-users] Corrupted pictures after date change?

[woenx]

Today I noticed that some of the pictures I had previously edited earlier
this morning had been corrupted. They could still be opened, but they were
all distorted, with parts missing, weird lines and color changes.

It's no big deal since I had a backup and I could restore them, but it's
kinda scary that this could happen without noticing and without any warning.
I only detected the corruption when I opened one of the pictures by chance,
since the thumbnail still displayed the correct image.

I'm still trying to figure out the cause. The corruption happened in
virtually all the pictures in which the date was changed (using the metadata
edit option in digikam). My pictures are stored in a NAS, and currently the
database is the NAS as well (I know, I'm just experimenting). Could this be
the cause?

I'm using digikam 6.0git in windows 10 64bit, by the way.

Has anyone else experienced something similar?



--
Sent from: http://digikam.1695700.n4.nabble.com/digikam-users-f1735189.html

[Gilles Caulier-4]

Which kind of file format exactly ? JPEG, PNG, TIFF, RAW ?

Gilles Caulier

2018-05-21 19:44 GMT+02:00 woenx <[hidden email]>:

Today I noticed that some of the pictures I had previously edited earlier
this morning had been corrupted. They could still be opened, but they were
all distorted, with parts missing, weird lines and color changes.

It's no big deal since I had a backup and I could restore them, but it's
kinda scary that this could happen without noticing and without any warning.
I only detected the corruption when I opened one of the pictures by chance,
since the thumbnail still displayed the correct image.

I'm still trying to figure out the cause. The corruption happened in
virtually all the pictures in which the date was changed (using the metadata
edit option in digikam). My pictures are stored in a NAS, and currently the
database is the NAS as well (I know, I'm just experimenting). Could this be
the cause?

I'm using digikam 6.0git in windows 10 64bit, by the way.

Has anyone else experienced something similar?



--
Sent from: http://digikam.1695700.n4.nabble.com/digikam-users-f1735189.html

[woenx]

JPG pictures. I don't know if it matters, by they are scans of old pictures.
I can share a few samples with you (along with the uncorrupted picture) if
you want to.



--
Sent from: http://digikam.1695700.n4.nabble.com/digikam-users-f1735189.html

[Gilles Caulier-4]

Yes, please share. and also give me some info about the camera used to take JPEG.

Gilles Caulier

2018-05-21 20:41 GMT+02:00 woenx <[hidden email]>:

JPG pictures. I don't know if it matters, by they are scans of old pictures.
I can share a few samples with you (along with the uncorrupted picture) if
you want to.

--
Sent from: http://digikam.1695700.n4.nabble.com/digikam-users-f1735189.html

[Gilles Caulier-4]

If you can reproduce the workflow to corrupt a JPG file, i can be very instructive to see all debug statements generated in background when file is modified by Exiv2 shared library in background when date is patched.

To catch debug statements under windows, you need to install debugview tool from Microsoft, run it, run digiKam, and look debug traces generated by digiKam while running.

https://docs.microsoft.com/en-us/sysinternals/downloads/debugview

Best

Gilles Caulier

2018-05-21 23:41 GMT+02:00 Gilles Caulier <[hidden email]>:

Yes, please share. and also give me some info about the camera used to take JPEG.

Gilles Caulier

2018-05-21 20:41 GMT+02:00 woenx <[hidden email]>:

JPG pictures. I don't know if it matters, by they are scans of old pictures.
I can share a few samples with you (along with the uncorrupted picture) if
you want to.

--
Sent from: http://digikam.1695700.n4.nabble.com/digikam-users-f1735189.html

[woenx]

Unfortunately, I have not been able to reproduce the workflow. I've tagged
and dated many other pictures since this morning, and they all seem to be
fine.

Basically I selected a picture, I went to tools, "Edit Metadata", and
changed the "Creation date and time", that's it. All pictures in the same
folder became corrupted.

It seems to be a one time thing. Maybe due to temporary low bandwidth (my
wifi ranges from 3-5MB/s), or maybe the SQLite database (which is stored in
a samba share) could not be accessed for a moment and caused this. I don't
know.

You can check the corrupted files here:
https://drive.google.com/drive/folders/1aKRTH-9n5SBOggLNLjOp7ig7XXQdQopB?usp=sharing

And here there are the exact same pictures, without corruption:
https://drive.google.com/drive/folders/16lGxbwTTfrCjNMfR5fV6EBUMnhaVWvcM?usp=sharing



--
Sent from: http://digikam.1695700.n4.nabble.com/digikam-users-f1735189.html