Bug 305918

Summary:	File->Save changes does not always hide the original
Product:	[Applications] digikam	Reporter:	Anders Lund <anderslund>
Component:	Albums-Versioning	Assignee:	Digikam Developers <digikam-bugs-null>
Status:	RESOLVED FIXED
Severity:	normal	CC:	caulier.gilles
Priority:	NOR
Version:	2.8.0
Target Milestone:	---
Platform:	unspecified
OS:	Linux
Latest Commit:		Version Fixed In:	5.8.0
Sentry Crash Report:

Description Anders Lund 2012-08-28 09:17:27 UTC

I tend to shoot in raw, and edit each worth-while image individually, pressing F4, making my changes and then "save changes". This is a fine workflow for me, and works well most of the time: When the converted, edit image is saved, the raw file is hidden, and tags and marks are applied ot both files. But in som cases - 10-15% maybe, for some reason the raw file is not hidden. The edited file is saved with the same name as when things works, but something goes wrong.

I hope this can be fixed, since the versioning is a nice functionality and lets me get things done in a very nice fashion! 

Reproducible: Sometimes

Comment 1 Marcel Wiesweg 2012-08-30 19:35:10 UTC

This requires more investigation. Please choose a pair of pictures where the original did not get properly hidden
1) Please give the XMP metadata, e.g. with "exiv2 -p x filename"
2) Please try to "Reread image metadata" for the edited version. Does it properly update the relation?

Comment 2 caulier.gilles 2015-07-01 06:03:27 UTC

New digiKam 4.11.0 is available :

https://www.digikam.org/node/740

Can you reproduce the problem with this release ?

Comment 3 caulier.gilles 2015-08-21 07:05:57 UTC

digiKam 4.12.0 is out :

https://www.digikam.org/node/741

We need a fresh feedback using this release please...
Thanks in advance.

Comment 4 caulier.gilles 2016-07-15 20:56:48 UTC

Anders,

What's about this file using last 5.0.0 ?

Gilles Caulier

Comment 5 caulier.gilles 2016-11-21 16:07:25 UTC

We need feedback with last digiKam AppImage Linux Bundle:

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

Gilles Caulier

Comment 6 caulier.gilles 2016-11-26 10:34:19 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 7 caulier.gilles 2017-04-16 20:09:40 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 8 caulier.gilles 2017-06-22 21:38:38 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 9 caulier.gilles 2017-11-30 09:30:29 UTC

Please update this entry from bugzilla with current 5.8.0 pre-release bundle to see if problem remain.

https://files.kde.org/digikam/

Thanks in advance

Gilles Caulier

Comment 10 Anders Lund 2017-11-30 09:58:40 UTC

I have changed my workflow completely, I am not using the built-in
editor any longerm nor am I using grouping. For me, this issue can be
closed.

På Thu, 30 Nov 2017 09:30:29 +0000
<bugzilla_noreply@kde.org> skrev:
> https://bugs.kde.org/show_bug.cgi?id=305918
> 
> --- Comment #9 from caulier.gilles@gmail.com ---
> Please update this entry from bugzilla with current 5.8.0 pre-release
> bundle to see if problem remain.
> 
> https://files.kde.org/digikam/
> 
> Thanks in advance
> 
> Gilles Caulier
>

Comment 11 caulier.gilles 2017-11-30 10:57:37 UTC

Thanks for the feedback. I close this file now...

Gilles Caulier