Bug 380260 - Sidecar files are not being created still
Summary: Sidecar files are not being created still
Status: RESOLVED FIXED
Alias: None
Product: digikam
Classification: Applications
Component: Metadata-Sidecar (show other bugs)
Version: 5.6.0
Platform: Appimage Linux
: NOR normal
Target Milestone: ---
Assignee: Digikam Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-05-27 20:10 UTC by Andrius
Modified: 2017-05-29 14:30 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In: 5.6.0

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Andrius 2017-05-27 20:10:34 UTC 
Continuation https://bugs.kde.org/show_bug.cgi?id=379833

Tested on 5.6.0 appimage

If there is no sidecar created yet for a video file and you add GPS coordinates to that video Geolocation Editor will still show an error instead.
Workaround is to go Item - Write metadata to file which creates a sidecar and apply geotagging after that. 

I am wondering if there is a way to make digikam create a sidecar for a raw image or a video file after any information (tag, GPS, people, etc.) has been added to the database.
Comment 1 Maik Qualmann 2017-05-28 05:47:15 UTC 
Please wait a bit longer the AppImage is not been updated yet. The bug is already fixed.

Maik
Comment 2 caulier.gilles 2017-05-28 06:22:29 UTC 
Maik,

I updated the AppImage bundles yesterday...

Gilles
Comment 3 Maik Qualmann 2017-05-28 07:04:00 UTC 
Problem is not reproducible with the current AppImage. The sidecar file is created with the GEO data. No error dialog is shown.

Maik
Comment 4 Andrius 2017-05-28 17:49:33 UTC 
(In reply to Maik Qualmann from comment #3)
> Problem is not reproducible with the current AppImage. The sidecar file is
> created with the GEO data. No error dialog is shown.
> 
> Maik

Thank you Maik. I think I downloaded mine few days ago so I will download it again tonight and will give it a try. I will keep you posted.
Comment 5 Andrius 2017-05-29 14:25:39 UTC 
I just tested the latest appimage and confirmed that the bug fixed. Thank you Maik!