Bug 512689

Summary: `Write Metadata to File` in the Item menu does not work
Product: [Applications] digikam Reporter: telefonciek
Component: Metadata-ExifAssignee: Digikam Developers <digikam-bugs-null>
Status: RESOLVED FIXED    
Severity: normal CC: caulier.gilles, metzpinguin
Priority: NOR    
Version First Reported In: 8.8.0   
Target Milestone: ---   
Platform: Flatpak   
OS: Linux   
Latest Commit: https://invent.kde.org/graphics/digikam/-/commit/a34b4c3ec225a34b03844a180dde0f60aa5027f1 Version Fixed/Implemented In: 9.0.0
Sentry Crash Report:

Description telefonciek 2025-11-27 17:07:40 UTC 
SUMMARY

This problem was already reported on discourse: https://discuss.pixls.us/t/writing-metadata-to-image-files/48446

I don't want to change metadata of all of my files at once, I prefer editing my files and applying changes manually only when I am satisfied with the result.

STEPS TO REPRODUCE
1. Configure DikiKam to not update metadata in files automatically
2. Open and edit some metadata in a random file (like GPS or Tag)
3. press Write Metadata to File

OBSERVED RESULT

Source image files are not changed

EXPECTED RESULT

I should be able to see changes in my file now

SOFTWARE/OS VERSIONS
Linux/KDE Plasma:  Fedora 43
Flatpak release: 8.8.0

ADDITIONAL INFORMATION
Comment 1 Maik Qualmann 2025-11-27 17:17:43 UTC 
If writing is disabled in the digiKam settings under metadata, then even when a write operation is forced, only that operation will be performed, or none at all. That is intentional.

Maik
Comment 2 Maik Qualmann 2025-11-27 17:20:16 UTC 
Note that metadata should never be written unless explicitly allowed in the settings.

If you want to delay write operations, the Lazy Sync option might be of interest to you.

Maik
Comment 3 caulier.gilles 2025-11-27 17:29:30 UTC 
Also double check the application permissions to setup with FlatPak. Look links listed here for details:

https://www.digikam.org/download/binary/#linux-sandbox
Comment 4 telefonciek 2025-11-29 20:28:53 UTC 
> only that operation will be performed, or none at all. That is intentional.


If this is intentional, then in case of disabled synchronization with files this button should be greyed-out/disabled. Because having a button which does nothing may be a bit misleading for new users.
Comment 5 telefonciek 2025-11-29 20:30:31 UTC 
In mentioned thread, you can see that I am not the only person which got confused by current behavior.
Comment 6 Maik Qualmann 2025-11-29 21:38:52 UTC 
Git commit a34b4c3ec225a34b03844a180dde0f60aa5027f1 by Maik Qualmann.
Committed on 29/11/2025 at 21:37.
Pushed by mqualmann into branch 'master'.

disable metadata write action if no option is enabled in the setup
FIXED-IN: 8.9.0

M  +5    -3    core/app/main/digikamapp.cpp
M  +10   -5    core/libs/metadataengine/engine/metaenginesettings.cpp
M  +5    -0    core/libs/metadataengine/engine/metaenginesettings.h
M  +15   -0    core/libs/metadataengine/engine/metaenginesettingscontainer.cpp
M  +2    -0    core/libs/metadataengine/engine/metaenginesettingscontainer.h

https://invent.kde.org/graphics/digikam/-/commit/a34b4c3ec225a34b03844a180dde0f60aa5027f1