| Summary: | HUB : digiKam could warn when writing metadata to pictures fails | ||
|---|---|---|---|
| Product: | [Applications] digikam | Reporter: | Vlado Plaga <rechner> |
| Component: | Metadata-Hub | Assignee: | Digikam Developers <digikam-bugs-null> |
| Status: | REPORTED --- | ||
| Severity: | wishlist | CC: | benedekppeter, caulier.gilles, chandra.kant.eee17, einmaladresse_2, iwannaberich, janise, julien.t43+kde, metzpinguin, michael.c.brown1 |
| Priority: | NOR | ||
| Version: | 6.0.0 | ||
| Target Milestone: | --- | ||
| Platform: | Arch Linux | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
| Attachments: | attachment-1142-0.html | ||
|
Description
Vlado Plaga
2009-12-27 00:47:09 UTC
Can you take a look with digiKam 1.2.0 ? Gilles Caulier The bug is still valid in digiKam 1.2.0.
To reproduce: take two pictures, make one of the read-only ("chmod -w"). Then in digiKam change their rating, comment, whatever. Notice how only the writable file is really modified (if your setting is to save metadata in pictures at all), without digiKam giving you a warning. Changes to the read-only file are only saved in digiKam's database.
Vlado, This file still valid using digiKam 2.x serie ? Gilles Caulier Yes, digiKam 2.1.1 still does not say anything when "Metadata Writing Mode" is set to "Write to image only" and writing to the image is not possible, because it is write protected. There now is the new option "Write to XMP sidecar for read-only image only" and that seems to work as expected: in my test an XMP sidecar file was only created for the image that was not writable, when I tried to change metadata for two images. By the way: I got some strange output on the console during these tests: digikam(18574)/digikam (core) Digikam::CollectionScanner::scanAlbum: Folder does not exist or is not readable: "/daten/digicam/nijmegen/2011-10-08__12-25-40.jpg18574" digikam(18574)/digikam (core) Digikam::CollectionScanner::scanAlbum: Folder does not exist or is not readable: "/daten/digicam/nijmegen/2011-10-08__12-25-40.jpg" There were more path names ending in "18574" mentioned for other images. We still dont have that implemented. Would need some sort of unobtrusive warning. I would say digikam *should* warn user Anyway, an easier way to *reduce* the problem is providing a log file of metadata writing and log all failure with files and attempted changes. This bug is resolved in the latest version of Digicam 6.0.0 How it can be solved as no code have been committed in this file ? Maik, did you confirm this ? Gilles Caulier No, there is no change to the code here and no message recognizable to the normal user. Maik So, why Chandra Kant can judge that this entry can be close !!! Gilles Caulier I am using digikam version 6.0.0 and when i used metadata hub it worked fine.I think that this problem was with the previous version. Created attachment 118500 [details] attachment-1142-0.html I am trying to contribute to that issue. On Sun, Mar 3, 2019 at 3:24 AM Maik Qualmann <bugzilla_noreply@kde.org> wrote: > https://bugs.kde.org/show_bug.cgi?id=220204 > > Maik Qualmann <metzpinguin@gmail.com> changed: > > What |Removed |Added > > ---------------------------------------------------------------------------- > CC| |metzpinguin@gmail.com > > --- Comment #9 from Maik Qualmann <metzpinguin@gmail.com> --- > No, there is no change to the code here and no message recognizable to the > normal user. > > Maik > > -- > You are receiving this mail because: > You are on the CC list for the bug. As the original reporter I can confirm that this problem still exists with digiKam 6.0 (under Arch Linux ARM). I chose "Image tags", "Captions and title", and "Rating" under "Write this information to metadata" (Configure / Metadata / Behaviour), then tried to change the title of a read-only file. In a writeable directory I get the following output on the terminal I started digiKam from: digikam.metaengine: File "IMG_20190209_112357.jpg" is read only. Metadata not written. digikam.metaengine: Will write XMP sidecar for file "IMG_20190209_112357.jpg" digikam.metaengine: wroteEXIF: true ... digikam.metaengine: Metadata for file "IMG_20190209_112357.jpg" written to XMP sidecar. When the directory also is read-only, the following is printed: digikam.metaengine: File "IMG_20190209_112357.jpg" is read only. Metadata not written. digikam.metaengine: Will write XMP sidecar for file "IMG_20190209_112357.jpg" digikam.metaengine: Cannot save metadata to XMP sidecar using Exiv2 (Error # 10 : /daten/digicam/2019/test_ro3/IMG_20190209_112357.jpg.xmp: Failed to open file (w+b): Permission denied (errno = 13) There is no output for a "normal" user, who is not watching his terminal. I think this can be a severe problem, and would like to see a notification. Maybe the operating system's notification system could be used, like for when a folder refresh (triggered by a right-click in the album tree) is completed? *** Bug 256784 has been marked as a duplicate of this bug. *** Yes,I agree Vlado Plaga that a notification must be shown regarding this issue for a normal user.I think that this issue arises because of read-only file. digiKam 7.0.0 stable release is now published: https://www.digikam.org/news/2020-07-19-7.0.0_release_announcement/ We need a fresh feedback on this file using this version. Best Regards Gilles Caulier *** Bug 434246 has been marked as a duplicate of this bug. *** *** Bug 461402 has been marked as a duplicate of this bug. *** *** Bug 391891 has been marked as a duplicate of this bug. *** *** Bug 463059 has been marked as a duplicate of this bug. *** |