[digikam] [Bug 420710] Shouldn't 'Exif.Image.DateTimeOriginal' be the equivalent of 'XMP Creation date' and 'IPTC Creation date', instead of Exif.Image.DateTime?

2021-09-05 Thread jm7
https://bugs.kde.org/show_bug.cgi?id=420710 j...@acm.org changed: What|Removed |Added CC||j...@acm.org --- Comment #23 from j...@acm.org

[digikam] [Bug 442040] New: Date time original does not always update correctly on maintenance read from image files.

2021-09-05 Thread jm7
https://bugs.kde.org/show_bug.cgi?id=442040 Bug ID: 442040 Summary: Date time original does not always update correctly on maintenance read from image files. Product: digikam Version: 7.4.0 Platform: Other

[digikam] [Bug 144858] Add a new BQM tool to permit batch metadata editing

2021-09-08 Thread jm7
https://bugs.kde.org/show_bug.cgi?id=144858 j...@acm.org changed: What|Removed |Added CC||j...@acm.org --- Comment #22 from j...@acm.org

[digikam] [Bug 144858] Add a new BQM tool to permit batch metadata editing

2021-09-08 Thread jm7
https://bugs.kde.org/show_bug.cgi?id=144858 --- Comment #23 from j...@acm.org --- Part of the confusion is, I believe that the original developer was thing of templates as an end point rather than a step on the journey. The template that was applied looks like it is stored in the database

[digikam] [Bug 440392] New: No entry field for Province/State in "Edit XMP" "Credits" tab of Metadata Editor

2021-07-29 Thread jm7
https://bugs.kde.org/show_bug.cgi?id=440392 Bug ID: 440392 Summary: No entry field for Province/State in "Edit XMP" "Credits" tab of Metadata Editor Product: digikam Version: 7.4.0 Platform: Other OS: Other

[digikam] [Bug 440363] New: Missing entry field for State/Province in Metadata Editor.

2021-07-28 Thread jm7
https://bugs.kde.org/show_bug.cgi?id=440363 Bug ID: 440363 Summary: Missing entry field for State/Province in Metadata Editor. Product: digikam Version: 7.4.0 Platform: Other OS: Other Status:

[digikam] [Bug 231114] TEMPLATE : Empty (unset) fields of template overwrite existing used fields when applying template

2021-07-21 Thread jm7
https://bugs.kde.org/show_bug.cgi?id=231114 j...@acm.org changed: What|Removed |Added CC||j...@acm.org --- Comment #11 from j...@acm.org

[digikam] [Bug 440015] New: Metadata Template insists on putting in a country name.

2021-07-18 Thread jm7
https://bugs.kde.org/show_bug.cgi?id=440015 Bug ID: 440015 Summary: Metadata Template insists on putting in a country name. Product: digikam Version: 7.3.0 Platform: Other OS: Microsoft Windows

[digikam] [Bug 302527] TEMPLATE : metadata editing not possible (copyright, city, ...)

2021-07-18 Thread jm7
https://bugs.kde.org/show_bug.cgi?id=302527 j...@acm.org changed: What|Removed |Added CC||j...@acm.org --- Comment #21 from j...@acm.org

[digikam] [Bug 440015] Metadata Template insists on putting in a country name.

2021-07-19 Thread jm7
https://bugs.kde.org/show_bug.cgi?id=440015 --- Comment #2 from j...@acm.org --- There is an error in the UI that was causing confusion. There is an OK button and a Cancel button. If there are never changes applied by the OK button, but instead it is some process in the dialog that needs to be

[digikam] [Bug 474677] Deleting files generates an error about permissions on .dtrash

2023-09-18 Thread jm7
https://bugs.kde.org/show_bug.cgi?id=474677 --- Comment #1 from j...@acm.org --- Found an anomaly that seems to have caused the problem. Unfortunately, this only pushes the problem back a level, and does not fix it. I discovered that there were about 1700 files in .dtrash\info that did not

[digikam] [Bug 474677] New: Deleting files generates an error about permissions on .dtrash

2023-09-18 Thread jm7
https://bugs.kde.org/show_bug.cgi?id=474677 Bug ID: 474677 Summary: Deleting files generates an error about permissions on .dtrash Classification: Applications Product: digikam Version: 8.2.0 Platform: Microsoft

[digikam] [Bug 473436] New: Digikam Sometimes hangs when the editor saves.

2023-08-15 Thread jm7
https://bugs.kde.org/show_bug.cgi?id=473436 Bug ID: 473436 Summary: Digikam Sometimes hangs when the editor saves. Classification: Applications Product: digikam Version: 8.2.0 Platform: Microsoft Windows OS: Microsoft

[digikam] [Bug 231114] TEMPLATE : Empty (unset) fields of template overwrite existing used fields when applying template

2022-08-01 Thread jm7
https://bugs.kde.org/show_bug.cgi?id=231114 --- Comment #12 from j...@acm.org --- I've just verified it's still in the most recent weekly: Build date: 7/29/2022 7:40 AM (target: RelWithDebInfo) Revision: 19a12d8a1716782631c1544138d6ba67dcb1913e Branch: qt5-maintenance -- You are receiving

[digikam] [Bug 231114] TEMPLATE : Empty (unset) fields of template overwrite existing used fields when applying template

2022-08-01 Thread jm7
https://bugs.kde.org/show_bug.cgi?id=231114 --- Comment #13 from j...@acm.org --- I've just verified it's still in the most recent weekly: Build date: 7/29/2022 7:40 AM (target: RelWithDebInfo) Revision: 19a12d8a1716782631c1544138d6ba67dcb1913e Branch: qt5-maintenance I also noticed that there

[digikam] [Bug 458584] New: Reverse Geocode information is not being updated correctly from external file edits.

2022-08-31 Thread jm7
https://bugs.kde.org/show_bug.cgi?id=458584 Bug ID: 458584 Summary: Reverse Geocode information is not being updated correctly from external file edits. Product: digikam Version: 7.8.0 Platform: Other OS:

[digikam] [Bug 410425] Wishlist: Reverse geocoding to IPTC/XMP location fields.

2022-08-31 Thread jm7
https://bugs.kde.org/show_bug.cgi?id=410425 j...@acm.org changed: What|Removed |Added CC||j...@acm.org --- Comment #3 from j...@acm.org

[digikam] [Bug 458583] New: Typos are not correctable in at least some fields in IPTC metadata.

2022-08-31 Thread jm7
https://bugs.kde.org/show_bug.cgi?id=458583 Bug ID: 458583 Summary: Typos are not correctable in at least some fields in IPTC metadata. Product: digikam Version: 7.8.0 Platform: Microsoft Windows OS:

[digikam] [Bug 464475] New: It would be nice if auto crop also worked with black borders,and not just white borders.

2023-01-18 Thread jm7
https://bugs.kde.org/show_bug.cgi?id=464475 Bug ID: 464475 Summary: It would be nice if auto crop also worked with black borders,and not just white borders. Classification: Applications Product: digikam Version: 7.8.0

[digikam] [Bug 465791] New: File rename does not work correctly if a single file is selected.

2023-02-15 Thread jm7
https://bugs.kde.org/show_bug.cgi?id=465791 Bug ID: 465791 Summary: File rename does not work correctly if a single file is selected. Classification: Applications Product: digikam Version: 7.10.0 Platform: Microsoft

[digikam] [Bug 471176] Setting multiple tags on multiple images does not work.

2023-06-17 Thread jm7
https://bugs.kde.org/show_bug.cgi?id=471176 --- Comment #1 from j...@acm.org --- After reviewing the bug symptoms more, this needs to be marked as MAJOR as there is data loss. -- You are receiving this mail because: You are watching all bug changes.

[digikam] [Bug 471176] New: Setting multiple tags on multiple images does not work.

2023-06-17 Thread jm7
https://bugs.kde.org/show_bug.cgi?id=471176 Bug ID: 471176 Summary: Setting multiple tags on multiple images does not work. Classification: Applications Product: digikam Version: 8.1.0 Platform: Microsoft Windows

[digikam] [Bug 471176] Setting multiple tags on multiple images does not work.

2023-06-19 Thread jm7
https://bugs.kde.org/show_bug.cgi?id=471176 --- Comment #5 from j...@acm.org --- I've noticed a bit of new information. Apparently, it works until the Geo Tag is done for a set of images. This has started happening in the last few beta releases. I've tried with the image database with the

[digikam] [Bug 479900] Strongly request a message about switching to Maria DB at 50K files.

2024-01-20 Thread jm7
https://bugs.kde.org/show_bug.cgi?id=479900 --- Comment #6 from j...@acm.org --- (In reply to Maik Qualmann from comment #2) > Corrupt files are not caused by the database used. As Gilles already writes, > what do you mean by "corrupt", files no longer readable or just missing > metadata. > We

[digikam] [Bug 479900] Strongly request a message about switching to Maria DB at 50K files.

2024-01-21 Thread jm7
https://bugs.kde.org/show_bug.cgi?id=479900 --- Comment #7 from j...@acm.org --- Created attachment 165111 --> https://bugs.kde.org/attachment.cgi?id=165111=edit Clear tag error. Ok. Now the problem has started with Maria DB. This is the first problem I have seen. I did have a hang

[digikam] [Bug 479900] Strongly request a message about switching to Maria DB at 50K files.

2024-01-21 Thread jm7
https://bugs.kde.org/show_bug.cgi?id=479900 --- Comment #8 from j...@acm.org --- Created attachment 165112 --> https://bugs.kde.org/attachment.cgi?id=165112=edit after adding a tag. to the file with the problem. I added a tag to the image with the problem, and all the tags magically

[digikam] [Bug 478623] MetadataEdit contents are disabled.

2023-12-17 Thread jm7
https://bugs.kde.org/show_bug.cgi?id=478623 --- Comment #2 from j...@acm.org --- Ok. Somehow, the entire collection ended up read only. I have no idea how that happened. -- You are receiving this mail because: You are watching all bug changes.

[digikam] [Bug 478623] New: Metadata (CTRL-ALT-M) disabled

2023-12-16 Thread jm7
https://bugs.kde.org/show_bug.cgi?id=478623 Bug ID: 478623 Summary: Metadata (CTRL-ALT-M) disabled Classification: Applications Product: digikam Version: 8.2.0 Platform: Microsoft Windows OS: Microsoft Windows

[digikam] [Bug 479758] New: Loss of data

2024-01-13 Thread jm7
https://bugs.kde.org/show_bug.cgi?id=479758 Bug ID: 479758 Summary: Loss of data Classification: Applications Product: digikam Version: 8.3.0 Platform: Microsoft Windows OS: Microsoft Windows Status: REPORTED

[digikam] [Bug 479900] New: Strongly request a message about switching to Maria DB at 50K files.

2024-01-16 Thread jm7
https://bugs.kde.org/show_bug.cgi?id=479900 Bug ID: 479900 Summary: Strongly request a message about switching to Maria DB at 50K files. Classification: Applications Product: digikam Version: 8.3.0 Platform: Other

[digikam] [Bug 479900] Strongly request a message about switching to Maria DB at 50K files.

2024-01-20 Thread jm7
https://bugs.kde.org/show_bug.cgi?id=479900 --- Comment #3 from j...@acm.org --- (In reply to caulier.gilles from comment #1) > What do you means about "around 20k corrupted files" ? All tags stripped, and in some images, face tags were stripped. The images themselves ere ok (except for a

[digikam] [Bug 479900] Strongly request a message about switching to Maria DB at 50K files.

2024-01-20 Thread jm7
https://bugs.kde.org/show_bug.cgi?id=479900 --- Comment #4 from j...@acm.org --- (In reply to j...@acm.org from comment #0) > SUMMARY > *** > NOTE: If you are reporting a crash, please try to attach a backtrace with > debug symbols. > See >

[digikam] [Bug 479900] Strongly request a message about switching to Maria DB at 50K files.

2024-01-20 Thread jm7
https://bugs.kde.org/show_bug.cgi?id=479900 --- Comment #5 from j...@acm.org --- (In reply to Maik Qualmann from comment #2) > Corrupt files are not caused by the database used. As Gilles already writes, > what do you mean by "corrupt", files no longer readable or just missing > metadata. > We