Bug 427041

Summary: Geolocation information not being saved to the metadata
Product: [Applications] digikam Reporter: MarcP <iwannaberich>
Component: Geolocation-WorkflowAssignee: Digikam Developers <digikam-bugs-null>
Status: RESOLVED NOT A BUG    
Severity: normal CC: cat75, caulier.gilles, iwannaberich, metzpinguin
Priority: NOR    
Version: 7.1.0   
Target Milestone: ---   
Platform: Appimage   
OS: Linux   
Latest Commit: Version Fixed In: 7.2.0
Sentry Crash Report:

Description MarcP 2020-09-27 17:34:46 UTC 
SUMMARY

The metadata is not saved to the image (unlike regular keywords, that are saved just fine). I have experienced this issue every now and then, but I don't know what might be causing it. 


STEPS TO REPRODUCE
1. Go to the Geolocation tool
2. Drop the picture on the map
3. Click apply

OBSERVED RESULT
Changes are applied immediately (faster than usual), and the geolocation icon appears on top of the picture in thumbnail view. However, if you refresh the metadata, that geolocation has not been written.

EXPECTED RESULT
Geolocation information actually being written to the picture.

SOFTWARE/OS VERSIONS

This is happening in Ubuntu 18.04.5 LTS with Gnome.

I have tried it right now with digikam 7.1 (stable, appimage) and the digikam-7.2.0-beta1-20200920T074549-x86-64.appimage, with the same result. 


ADDITIONAL INFORMATION

Running digikam in debug mode does not show any errors when trying to save the metadata. I made sure the picture is writable by the user than runs digikam (and made sure I can write other kind of metadata without any issue).
Comment 1 Maik Qualmann 2020-09-27 18:37:39 UTC 
Hi Marc, we didn't already have the topic? ((:-))
There is a new setting in the metadata settings to enable writing of geolocation information. By default like all other write settings, deactivated. Geolocation information is now also synchronized when it is written later.

Maik
Comment 2 MarcP 2020-09-27 18:55:43 UTC 
Arg, I'm so sorry! It must have been that. It wasn't my usual computer, so I must have forgotten to enable that option again.
Comment 3 Maik Qualmann 2020-09-29 10:59:18 UTC 
*** Bug 427107 has been marked as a duplicate of this bug. ***