------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee. http://bugs.kde.org/show_bug.cgi?id=141960 Summary: Problems with photos without EXIV data when updating metadata of all photos Product: digikam Version: unspecified Platform: SuSE RPMs OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general AssignedTo: digikam-devel kde org ReportedBy: krienke uni-koblenz de Version: 0.9.1-rc1 (using KDE KDE 3.5.6) Installed from: SuSE RPMs Compiler: gcc 4.1.2 OS: Linux I selected menu "Tools->Sync all pictures metadata" to synchronize all the metadata that are in the database with the metadata that are in the photo files. For most of the photos this workes fine. However I had some JPG photo files that do not have any metadata in them (probably removed by another tool). However I had tags set on them and I chose to store the tags in the files IPTC metadata. After the synchronisation the photo still did not have metadata and there was no warning that the sync process did not work for this photo. So the problem is, that the tags set on the photo were not stored inside the photos metadata and there was no warning that this could not be done. _______________________________________________ Digikam-devel mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-devel |
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee. http://bugs.kde.org/show_bug.cgi?id=141960 caulier.gilles gmail com changed: What |Removed |Added ---------------------------------------------------------------------------- Component|general |Metadata ------- Additional Comments From caulier.gilles gmail com 2007-02-20 07:57 ------- krienke, start digiKAm from a console and try to reproduce the problem. Look if some error messages appears on the console, especialy from Exiv2 library. Note than digiKam must be compiled using "./configure --enable-debug=full" option Gilles _______________________________________________ Digikam-devel mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-devel |
Am Dienstag, 20. Februar 2007 07:57:34 schrieb Gilles Caulier:
> ------- You are receiving this mail because: ------- > You are the assignee for the bug, or are watching the assignee. > > start digiKAm from a console and try to reproduce the problem. Look if some > error messages appears on the console, especialy from Exiv2 library. I can see the problem now. The file in question had only read access (r-- --- ---) and digikam could not write to this file. What would be needed in this case is a warning about the problem. After I added write access to the file everything was fine. Rainer -- --------------------------------------------------------------------------- Rainer Krienke, Universitaet Koblenz, Rechenzentrum, Raum A022 Universitaetsstrasse 1, 56070 Koblenz, Tel: +49 261287 -1312, Fax: -1001312 Mail: [hidden email], Web: http://www.uni-koblenz.de/~krienke Get my public PGP key: http://www.uni-koblenz.de/~krienke/mypgp.html --------------------------------------------------------------------------- _______________________________________________ Digikam-devel mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-devel attachment0 (196 bytes) Download Attachment |
In reply to this post by krienke
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee. http://bugs.kde.org/show_bug.cgi?id=141960 ------- Additional Comments From krienke uni-koblenz de 2007-02-20 08:22 ------- Am Dienstag, 20. Februar 2007 07:57:34 schrieb Gilles Caulier: > ------- You are receiving this mail because: ------- > You are the assignee for the bug, or are watching the assignee. > > start digiKAm from a console and try to reproduce the problem. Look if some > error messages appears on the console, especialy from Exiv2 library. I can see the problem now. The file in question had only read access (r-- --- ---) and digikam could not write to this file. What would be needed in this case is a warning about the problem. After I added write access to the file everything was fine. Rainer _______________________________________________ Digikam-devel mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-devel |
Free forum by Nabble | Edit this page |