Bug 312661 - No error message if metadata edit fails due to insufficient file permissions
Summary: No error message if metadata edit fails due to insufficient file permissions
Status: RESOLVED DUPLICATE of bug 133515
Alias: None
Product: digikam
Classification: Applications
Component: Plugin-Generic-MetadataEdit (show other bugs)
Version: unspecified
Platform: Gentoo Packages Linux
: NOR normal
Target Milestone: ---
Assignee: Digikam Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-01-05 10:32 UTC by Peter Albrecht
Modified: 2023-10-24 05:44 UTC (History)
1 user (show)

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Peter Albrecht 2013-01-05 10:32:42 UTC
If you try to change Metadata of an image with insufficient file write permissions, the operation fails. But the user is not informed about this failure.

Reproducible: Always

Steps to Reproduce:
1. configure digikam to write tag in jpg files
2. take picture (jpg file) in digikam and assign a tag to it 
  => tag is written to IPTC information in the file
3. in Konsole: chmod a-w myPicture.jpg
4. in digiKam: select the picture and go to Image -> Metadata -> Edit All Metadata...
5. select Edit IPTC tab
6. select your tag (assigned above)
7. click "Delete"
8. press "OK" 
Actual Results:  
No error message is shown and the user thinks the changes are applied.
But "exiv2 -p a myPicture.jpg" in Konsole reveals, that the "Iptc.Application2.Keywords" (= tag) is still in the file.
Also the "Edit All Metadata..." dialog mentioned above, shows that the keyword/tag is still there.

Expected Results:  
An error message should be shown, like e.g.: "Could not update file metadata due to insufficient file permissions" 

As workaround (until this is fixed), the user could click "Apply" instead of "OK".
After clicking "Apply", the metadata seems to be reloaded from the file after the metadata change attempt. So the user sees the deleted tag to appear again. (Not nice, but better than no feedback)

I use KDE 4.9.3 and digiKam 2.9.0.
Comment 1 caulier.gilles 2013-07-08 08:54:17 UTC

*** This bug has been marked as a duplicate of bug 133515 ***
Comment 2 caulier.gilles 2023-10-24 05:44:45 UTC
Peter

The digiKam 8.2.0 pre-release for Windows is available for testing :

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

Problem still reproducible on your computer ?

Thanks in advance

Gilles Caulier