Bug 369636 - Batch time stamp adjusting causes digikam to crash and destroys photos
Summary: Batch time stamp adjusting causes digikam to crash and destroys photos
Status: RESOLVED FIXED
Alias: None
Product: digikam
Classification: Applications
Component: Plugin-Bqm-TimeAdjust (show other bugs)
Version: 4.14.0
Platform: Ubuntu Linux
: NOR critical
Target Milestone: ---
Assignee: Digikam Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-10-02 12:37 UTC by developer
Modified: 2017-06-27 11:30 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In: 5.7.0
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description developer 2016-10-02 12:37:36 UTC
When correcting the time stamps of photos, the app crashes. The bug was observed in digiKam 4.12, 4.14 and 5.2.0. Additionally some of the photos get destroyed in the process, only half images are preserved.

Reproducible: Always

Steps to Reproduce:
1. Select several photos
2. Open the Tools > Adjust Time and Date dialog
3. choose to overwrite any of the given metadata (exif, iptc)
4. Adjust time correction (only tested adding amount of time)
5. Start batch process
6. Crash
7. Reopen > some photos are destroyed, some have the correct time stamp, some are unchanged

Actual Results:  
digiKam crashes and some photos are lost or damaged

Expected Results:  
All selected photos should have the chosen time stamp now.

- Ubuntu 16.04 with exiv2 in version 0.25
- additionally tried the most recent digiKam versions of digikam 4 and digikam 5 from a ppa, same problem - maybe rather an exiv2 issue.
Comment 1 caulier.gilles 2016-11-02 15:38:54 UTC
We need a GDB backtrace to hack this problem.

Also please test with DK 5.3.0 AppImage.

https://drive.google.com/open?id=0BzeiVr-byqt5Y0tIRWVWelRJenM

Gilles Caulier
Comment 2 caulier.gilles 2016-11-21 16:02:46 UTC
We need feedback with last digiKam AppImage Linux Bundle:

https://drive.google.com/open?id=0BzeiVr-byqt5Y0tIRWVWelRJenM

Gilles Caulier
Comment 3 caulier.gilles 2016-11-26 10:34:22 UTC
This problem still reproducible using digiKam AppImage bundle 5.4.0 pre release
?

It available at this url :

https://drive.google.com/drive/folders/0BzeiVr-byqt5Y0tIRWVWelRJenM

Gilles Caulier
Comment 4 caulier.gilles 2017-04-16 20:07:06 UTC
digiKam 5.5.0 is released officially

https://download.kde.org/stable/digikam/

...and new 5.6.0 pre-release as bundle is available here :

https://drive.google.com/drive/folders/0BzeiVr-byqt5Y0tIRWVWelRJenM

Please check if this problem still reproducible with these versions.

Thanks in advance

Gilles Caulier
Comment 5 caulier.gilles 2017-06-22 21:38:52 UTC
digiKam 5.6.0 is now release and available as bundle for Linux, MacOS and Windows.

Can you check if problem still exists with this version ?

Thanks in advance

Gilles Caulier
Comment 6 caulier.gilles 2017-06-27 11:30:38 UTC
Not reproducible with 5.7.0 and no more user feedback. Closed.